CVE-2026-64027

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 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:

net: shaper: rework the VALID marking (again)

Recent commit changed the semantics from NOT_VALID to VALID. I didn't realize that the flags are not stored atomically with the entry in XArray. There's still a race of reader observing a VALID mark for a slot, getting interrupted, writer replacing the entry with a different one, reader continuing, fetching the entry which is now a different pointer than the pointer for which VALID was meant.

The biggest consequence of this is that we may see a UAF since net_shaper_rollback() assumed that entries without VALID can be freed without observing RCU.

Looks like the XArray marks are buying us nothing at this point. Let's convert the code to an explicit valid field. The smp_load_acquire() / smp_store_release() barriers are marginally cleaner.

CVSS v3
7.8
EG Score
7.8(medium)
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
3%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (3)

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

net: shaper: rework the VALID marking (again) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b8d7519352ba8c6df83259295d4a3bad093cae90
generic

net: shaper: rework the VALID marking (again) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/96ea960dd40fd55302e0fd755176f26a95e6a50c
generic

net: shaper: rework the VALID marking (again) - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2417df5e7bb4184b9d3a2988036bf2c46e594545

Vendor Advisories for CVE-2026-64027(1)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

All Vendor Advisories

(5)

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 33× in last 7d / 156× 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.

Showing the most recent 100 of 206 total refreshes for this CVE.

  1. 2026-08-30 02:52 UTCEG score recompute
  2. 2026-08-30 02:52 UTCVendor advisory
  3. 2026-08-30 02:52 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-28 03:30 UTCVendor advisory
  7. 2026-08-28 03:30 UTCGHSA enrichment
  8. 2026-08-27 15:15 UTCEG score recompute
  9. 2026-08-27 15:15 UTCVendor advisory
  10. 2026-08-27 15:15 UTCGHSA enrichment
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 02:12 UTCEG score recompute
  13. 2026-08-27 02:12 UTCVendor advisory
  14. 2026-08-27 02:12 UTCGHSA enrichment
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-26 13:59 UTCVendor advisory
  17. 2026-08-26 13:59 UTCGHSA enrichment
  18. 2026-08-26 01:46 UTCEG score recompute
  19. 2026-08-26 01:46 UTCVendor advisory
  20. 2026-08-26 01:46 UTCGHSA enrichment
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 13:33 UTCVendor advisory
  23. 2026-08-25 13:33 UTCGHSA enrichment
  24. 2026-08-25 01:20 UTCEG score recompute
  25. 2026-08-25 01:20 UTCVendor advisory
Show 75 more
  1. 2026-08-25 01:20 UTCGHSA enrichment
  2. 2026-08-24 13:05 UTCEG score recompute
  3. 2026-08-24 13:05 UTCVendor advisory
  4. 2026-08-24 13:05 UTCGHSA enrichment
  5. 2026-08-24 00:51 UTCVendor advisory
  6. 2026-08-24 00:51 UTCGHSA enrichment
  7. 2026-08-23 12:38 UTCVendor advisory
  8. 2026-08-23 12:38 UTCGHSA enrichment
  9. 2026-08-23 00:25 UTCEG score recompute
  10. 2026-08-23 00:25 UTCVendor advisory
  11. 2026-08-23 00:25 UTCGHSA enrichment
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 12:10 UTCVendor advisory
  14. 2026-08-22 12:10 UTCGHSA enrichment
  15. 2026-08-21 23:57 UTCEG score recompute
  16. 2026-08-21 23:57 UTCVendor advisory
  17. 2026-08-21 23:57 UTCGHSA enrichment
  18. 2026-08-21 23:49 UTCEPSS rescore
  19. 2026-08-21 11:43 UTCVendor advisory
  20. 2026-08-21 11:43 UTCGHSA enrichment
  21. 2026-08-20 23:27 UTCEG score recompute
  22. 2026-08-20 23:27 UTCVendor advisory
  23. 2026-08-20 23:27 UTCGHSA enrichment
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 11:14 UTCVendor advisory
  26. 2026-08-20 11:14 UTCGHSA enrichment
  27. 2026-08-19 23:01 UTCEG score recompute
  28. 2026-08-19 23:01 UTCVendor advisory
  29. 2026-08-19 23:01 UTCGHSA enrichment
  30. 2026-08-19 17:04 UTCEPSS rescore
  31. 2026-08-19 10:05 UTCVendor advisory
  32. 2026-08-19 10:04 UTCGHSA enrichment
  33. 2026-08-18 21:49 UTCEG score recompute
  34. 2026-08-18 21:49 UTCVendor advisory
  35. 2026-08-18 21:49 UTCGHSA enrichment
  36. 2026-08-18 09:23 UTCVendor advisory
  37. 2026-08-18 09:23 UTCGHSA enrichment
  38. 2026-08-17 21:08 UTCEG score recompute
  39. 2026-08-17 21:08 UTCVendor advisory
  40. 2026-08-17 21:08 UTCGHSA enrichment
  41. 2026-08-17 13:47 UTCEPSS rescore
  42. 2026-08-17 07:26 UTCVendor advisory
  43. 2026-08-17 07:26 UTCGHSA enrichment
  44. 2026-08-16 19:13 UTCEG score recompute
  45. 2026-08-16 19:13 UTCVendor advisory
  46. 2026-08-16 19:13 UTCGHSA enrichment
  47. 2026-08-16 14:56 UTCEPSS rescore
  48. 2026-08-16 06:27 UTCEG score recompute
  49. 2026-08-16 06:27 UTCVendor advisory
  50. 2026-08-16 06:27 UTCGHSA enrichment
  51. 2026-08-15 18:15 UTCVendor advisory
  52. 2026-08-15 18:15 UTCGHSA enrichment
  53. 2026-08-15 06:02 UTCEG score recompute
  54. 2026-08-15 06:02 UTCVendor advisory
  55. 2026-08-15 06:02 UTCGHSA enrichment
  56. 2026-08-15 01:30 UTCEPSS rescore
  57. 2026-08-14 17:48 UTCVendor advisory
  58. 2026-08-14 17:48 UTCGHSA enrichment
  59. 2026-08-14 05:35 UTCEG score recompute
  60. 2026-08-14 05:35 UTCVendor advisory
  61. 2026-08-14 05:35 UTCGHSA enrichment
  62. 2026-08-13 22:00 UTCEPSS rescore
  63. 2026-08-13 17:22 UTCVendor advisory
  64. 2026-08-13 17:22 UTCGHSA enrichment
  65. 2026-08-13 05:08 UTCVendor advisory
  66. 2026-08-13 05:08 UTCGHSA enrichment
  67. 2026-08-12 16:56 UTCEG score recompute
  68. 2026-08-12 16:56 UTCVendor advisory
  69. 2026-08-12 16:56 UTCGHSA enrichment
  70. 2026-08-12 13:51 UTCEPSS rescore
  71. 2026-08-12 04:43 UTCVendor advisory
  72. 2026-08-12 04:43 UTCGHSA enrichment
  73. 2026-08-11 16:30 UTCEG score recompute
  74. 2026-08-11 16:30 UTCVendor advisory
  75. 2026-08-11 16:30 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-64027?
CVE-2026-64027 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: net: shaper: rework the VALID marking (again) Recent commit changed the semantics from NOT_VALID to VALID. I didn't realize that the flags are not stored atomically with the entry in XArray. There's still a race of reader observing…
When was CVE-2026-64027 disclosed?
CVE-2026-64027 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64027 actively exploited?
CVE-2026-64027 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 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-64027?
CVE-2026-64027 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64027?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64027, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64027

Explore →

Is Your Infrastructure Affected by CVE-2026-64027?

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

Start Free Scan →Browse All CVEs