CVE-2026-64073

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:

irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT

On PREEMPT_RT, non-HARD irq_work runs in per-CPU kthreads via run_irq_workd(), so irq_work_sync() uses rcuwait() to wait for BUSY==0.

After irq_work_single() clears BUSY via atomic_cmpxchg(), it still dereferences @work for irq_work_is_hard() and rcuwait_wake_up().

An irq_work_sync() caller on another CPU that enters after BUSY is cleared can observe BUSY==0 immediately, return, and free the work before those accesses complete — causing a use-after-free.

Fix this by wrapping run_irq_workd() in guard(rcu)() so that the entire irq_work_single() execution is within an RCU read-side critical section. Then add synchronize_rcu() in irq_work_sync() after rcuwait_wait_event() to ensure the caller waits for the RCU grace period before returning, preventing premature frees.

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 (6)

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

irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT - kernel/git/stable/linux.git - Linux kernel stable tree

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

irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/91840be8f710370607f949a627e070896faeddb8
generic

irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/81b582784518196eff1050212a046bc29d3a05dd
generic

irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/684a78183c54c23e70d1cba320f7fc184604210b
generic

irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2dc79362302922cb18f35e262712b5e58de65442
generic

irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18c0456ea2615b1a743a6db739c74411c3b42bc6

Vendor Advisories for CVE-2026-64073(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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
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 31× in last 7d / 162× 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:50 UTCEG score recompute
  2. 2026-08-30 02:50 UTCVendor advisory
  3. 2026-08-30 02:50 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 23:48 UTCEG score recompute
  7. 2026-08-27 23:48 UTCVendor advisory
  8. 2026-08-27 23:48 UTCGHSA enrichment
  9. 2026-08-27 11:48 UTCVendor advisory
  10. 2026-08-27 11:48 UTCGHSA enrichment
  11. 2026-08-26 22:17 UTCEG score recompute
  12. 2026-08-26 22:16 UTCGHSA enrichment
  13. 2026-08-26 14:46 UTCEPSS rescore
  14. 2026-08-26 07:23 UTCVendor advisory
  15. 2026-08-26 07:23 UTCGHSA enrichment
  16. 2026-08-25 18:46 UTCEG score recompute
  17. 2026-08-25 18:46 UTCVendor advisory
  18. 2026-08-25 18:46 UTCGHSA enrichment
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 07:00 UTCVendor advisory
  21. 2026-08-25 07:00 UTCGHSA enrichment
  22. 2026-08-24 19:23 UTCEG score recompute
  23. 2026-08-24 19:23 UTCVendor advisory
  24. 2026-08-24 19:23 UTCGHSA enrichment
  25. 2026-08-24 07:45 UTCVendor advisory
Show 75 more
  1. 2026-08-24 07:45 UTCGHSA enrichment
  2. 2026-08-23 20:00 UTCVendor advisory
  3. 2026-08-23 20:00 UTCGHSA enrichment
  4. 2026-08-23 08:22 UTCEG score recompute
  5. 2026-08-23 08:22 UTCVendor advisory
  6. 2026-08-23 08:22 UTCGHSA enrichment
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-22 20:45 UTCVendor advisory
  9. 2026-08-22 20:45 UTCGHSA enrichment
  10. 2026-08-22 09:07 UTCEG score recompute
  11. 2026-08-22 09:07 UTCVendor advisory
  12. 2026-08-22 09:07 UTCGHSA enrichment
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 21:29 UTCVendor advisory
  15. 2026-08-21 21:29 UTCGHSA enrichment
  16. 2026-08-21 09:52 UTCEG score recompute
  17. 2026-08-21 09:52 UTCVendor advisory
  18. 2026-08-21 09:52 UTCGHSA enrichment
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 22:14 UTCVendor advisory
  21. 2026-08-20 22:14 UTCGHSA enrichment
  22. 2026-08-20 10:36 UTCVendor advisory
  23. 2026-08-20 10:36 UTCGHSA enrichment
  24. 2026-08-19 22:59 UTCEG score recompute
  25. 2026-08-19 22:59 UTCVendor advisory
  26. 2026-08-19 22:59 UTCGHSA enrichment
  27. 2026-08-19 17:04 UTCEPSS rescore
  28. 2026-08-19 07:25 UTCVendor advisory
  29. 2026-08-19 07:25 UTCGHSA enrichment
  30. 2026-08-18 19:47 UTCEG score recompute
  31. 2026-08-18 19:47 UTCVendor advisory
  32. 2026-08-18 19:47 UTCGHSA enrichment
  33. 2026-08-18 03:41 UTCVendor advisory
  34. 2026-08-18 03:41 UTCGHSA enrichment
  35. 2026-08-17 15:55 UTCEG score recompute
  36. 2026-08-17 15:55 UTCVendor advisory
  37. 2026-08-17 15:55 UTCGHSA enrichment
  38. 2026-08-17 13:47 UTCEPSS rescore
  39. 2026-08-17 04:18 UTCVendor advisory
  40. 2026-08-17 04:18 UTCGHSA enrichment
  41. 2026-08-16 16:41 UTCEG score recompute
  42. 2026-08-16 16:41 UTCVendor advisory
  43. 2026-08-16 16:41 UTCGHSA enrichment
  44. 2026-08-16 14:56 UTCEPSS rescore
  45. 2026-08-16 05:03 UTCEG score recompute
  46. 2026-08-16 05:03 UTCVendor advisory
  47. 2026-08-16 05:03 UTCGHSA enrichment
  48. 2026-08-15 17:26 UTCVendor advisory
  49. 2026-08-15 17:26 UTCGHSA enrichment
  50. 2026-08-15 05:49 UTCEG score recompute
  51. 2026-08-15 05:49 UTCVendor advisory
  52. 2026-08-15 05:49 UTCGHSA enrichment
  53. 2026-08-15 01:30 UTCEPSS rescore
  54. 2026-08-14 18:11 UTCVendor advisory
  55. 2026-08-14 18:11 UTCGHSA enrichment
  56. 2026-08-14 06:34 UTCEG score recompute
  57. 2026-08-14 06:34 UTCVendor advisory
  58. 2026-08-14 06:34 UTCGHSA enrichment
  59. 2026-08-13 22:00 UTCEPSS rescore
  60. 2026-08-13 18:56 UTCVendor advisory
  61. 2026-08-13 18:56 UTCGHSA enrichment
  62. 2026-08-13 07:19 UTCVendor advisory
  63. 2026-08-13 07:18 UTCGHSA enrichment
  64. 2026-08-12 19:40 UTCEG score recompute
  65. 2026-08-12 19:40 UTCVendor advisory
  66. 2026-08-12 19:40 UTCGHSA enrichment
  67. 2026-08-12 13:51 UTCEPSS rescore
  68. 2026-08-12 08:03 UTCVendor advisory
  69. 2026-08-12 08:03 UTCGHSA enrichment
  70. 2026-08-11 20:26 UTCEG score recompute
  71. 2026-08-11 20:26 UTCVendor advisory
  72. 2026-08-11 20:26 UTCGHSA enrichment
  73. 2026-08-11 08:49 UTCEG score recompute
  74. 2026-08-11 08:49 UTCVendor advisory
  75. 2026-08-11 08:49 UTCGHSA enrichment

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-64073?
CVE-2026-64073 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: irqwork: Fix use-after-free in irqworksingle() on PREEMPTRT On PREEMPTRT, non-HARD irqwork runs in per-CPU kthreads via runirqworkd(), so irqworksync() uses rcuwait() to wait for BUSY==0. After irqworksingle() clears BUSY via…
When was CVE-2026-64073 disclosed?
CVE-2026-64073 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-64073 actively exploited?
CVE-2026-64073 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 96.9% of all scored CVEs.
What is the CVSS score of CVE-2026-64073?
CVE-2026-64073 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64073?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64073, 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-64073

Explore →

Is Your Infrastructure Affected by CVE-2026-64073?

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

Start Free Scan →Browse All CVEs