CVE-2026-63858

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

netfilter: nf_tables: add hook transactions for device deletions

Restore the flag that indicates that the hook is going away, ie. NFT_HOOK_REMOVE, but add a new transaction object to track deletion of hooks without altering the basechain/flowtable hook_list during the preparation phase.

The existing approach that moves the hook from the basechain/flowtable hook_list to transaction hook_list breaks netlink dump path readers of this RCU-protected list.

It should be possible use an array for nft_trans_hook to store the deleted hooks to compact the representation but I am not expecting many hook object, specially now that wildcard support for devices is in place.

Note that the nft_trans_chain_hooks() list contains a list of struct nft_trans_hook objects for DELCHAIN and DELFLOWTABLE commands, while this list stores struct nft_hook objects for NEWCHAIN and NEWFLOWTABLE. Note that new commands can be updated to use nft_trans_hook for consistency.

This patch also adapts the event notification path to deal with the list of hook transactions.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 20, 2026

Advisory Details (2)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

netfilter: nf_tables: add hook transactions for device deletions - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4e69bfb32b2db323d9205fdb30e284481b37817c
generic

netfilter: nf_tables: add hook transactions for device deletions - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/10f79dbd7719d1da9f5884d13060322d8729f091

Vendor Advisories for CVE-2026-63858(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-07-26ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-07-26ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 25× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 14:14 UTCEPSS rescore
  2. 2026-07-27 10:37 UTCGHSA enrichment
  3. 2026-07-26 22:50 UTCEG score recompute
  4. 2026-07-26 22:50 UTCVendor advisory
  5. 2026-07-26 22:50 UTCGHSA enrichment
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 11:04 UTCEG score recompute
  9. 2026-07-26 11:04 UTCVendor advisory
  10. 2026-07-26 11:04 UTCGHSA enrichment
  11. 2026-07-24 14:18 UTCEPSS rescore
  12. 2026-07-24 14:18 UTCEPSS rescore
  13. 2026-07-23 14:18 UTCEPSS rescore
  14. 2026-07-23 14:18 UTCEPSS rescore
  15. 2026-07-23 03:22 UTCEG score recompute
  16. 2026-07-22 14:08 UTCEPSS rescore
  17. 2026-07-22 14:08 UTCEPSS rescore
  18. 2026-07-21 15:25 UTCEPSS rescore
  19. 2026-07-21 15:25 UTCEPSS rescore
  20. 2026-07-20 17:40 UTCEG score recompute
  21. 2026-07-20 17:40 UTCGHSA enrichment
  22. 2026-07-20 17:08 UTCEPSS rescore
  23. 2026-07-20 14:42 UTCEG score recompute 7.80
  24. 2026-07-20 14:41 UTCGHSA enrichment
  25. 2026-07-20 14:32 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
Show 12 more
  1. 2026-07-19 17:42 UTCGHSA enrichment
  2. 2026-07-19 17:35 UTCGHSA enrichment
  3. 2026-07-19 17:14 UTCGHSA enrichment
  4. 2026-07-19 17:07 UTCGHSA enrichment
  5. 2026-07-19 17:06 UTCGHSA enrichment
  6. 2026-07-19 17:03 UTCGHSA enrichment
  7. 2026-07-19 17:01 UTCGHSA enrichment
  8. 2026-07-19 16:59 UTCGHSA enrichment
  9. 2026-07-19 15:58 UTCGHSA enrichment
  10. 2026-07-19 15:51 UTCNVD update
  11. 2026-07-19 14:35 UTCEG score recompute
  12. 2026-07-19 14:34 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-63858?
CVE-2026-63858 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: add hook transactions for device deletions Restore the flag that indicates that the hook is going away, ie. NFTHOOKREMOVE, but add a new transaction object to track deletion of hooks without altering the…
When was CVE-2026-63858 disclosed?
CVE-2026-63858 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63858 actively exploited?
CVE-2026-63858 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.4% of all scored CVEs.
What is the CVSS score of CVE-2026-63858?
CVE-2026-63858 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-63858?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63858, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-63858

Explore →

Is Your Infrastructure Affected by CVE-2026-63858?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.