CVE-2026-64435

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

audit: Fix data races of skb_queue_len() readers on audit_queue

Multiple readers access audit_queue.qlen via skb_queue_len() without holding the queue lock or using READ_ONCE(), while kauditd writes to this field via the skb_dequeue() → __skb_unlink() path with WRITE_ONCE() protected by a spinlock. This constitutes data races.

All affected skb_queue_len(&audit_queue) call sites:

  • kauditd_thread() wait_event_freezable() condition
  • audit_receive_msg() AUDIT_GET handler (s.backlog assignment)
  • audit_receive() backlog check
  • audit_log_start() backlog check and pr_warn()

KCSAN reports the following conflicting access pattern (one example): ================================================================== BUG: KCSAN: data-race in audit_log_start / skb_dequeue

write (marked) to 0xffffffff8512ee20 of 4 bytes by task 661 on cpu 57: skb_dequeue+0x70/0xf0 kauditd_send_queue+0x71/0x220 kauditd_thread+0x1cb/0x430 kthread+0x1c2/0x210 ret_from_fork+0x162/0x1a0 ret_from_fork_asm+0x1a/0x30

read to 0xffffffff8512ee20 of 4 bytes by task 36586 on cpu 1: audit_log_start+0x2a0/0x6b0 audit_core_dumps+0x64/0xa0 do_coredump+0x14b/0x1260 get_signal+0xeb2/0xf70 arch_do_signal_or_restart+0x41/0x170 exit_to_user_mode_loop+0xa2/0x1c0 do_syscall_64+0x1a3/0x1c0 entry_SYSCALL_64_after_hwframe+0x76/0xe0

value changed: 0x00000001 -> 0x00000000 ==================================================================

Resolve the race by switching to lockless helper skb_queue_len_lockless(), which internally uses READ_ONCE() and properly pairs with the WRITE_ONCE() write accesses already present on the writer side.

[PM: line length tweak]

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
42(Track)
EG Risk 42/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
Severity82% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

July 25, 2026

Last Modified

September 3, 2026

Advisory Details (8)

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

audit: Fix data races of skb_queue_len() readers on audit_queue - kernel/git/stable/linux.git - Linux kernel stable tree

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

audit: Fix data races of skb_queue_len() readers on audit_queue - kernel/git/stable/linux.git - Linux kernel stable tree

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

audit: Fix data races of skb_queue_len() readers on audit_queue - kernel/git/stable/linux.git - Linux kernel stable tree

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

audit: Fix data races of skb_queue_len() readers on audit_queue - kernel/git/stable/linux.git - Linux kernel stable tree

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

audit: Fix data races of skb_queue_len() readers on audit_queue - kernel/git/stable/linux.git - Linux kernel stable tree

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

audit: Fix data races of skb_queue_len() readers on audit_queue - kernel/git/stable/linux.git - Linux kernel stable tree

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

audit: Fix data races of skb_queue_len() readers on audit_queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ff42312ccde549f8c698723822c7db35107a39b
generic

audit: Fix data races of skb_queue_len() readers on audit_queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/69f98fff30bdaa72b0cb0e7e078ab6456a0a59b0

Vendor Advisories for CVE-2026-64435(2)

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

Patch Availability(5)

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

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.4-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 24× in last 7d / 120× 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 268 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64435?
CVE-2026-64435 is a high vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: audit: Fix data races of skbqueuelen() readers on audit_queue Multiple readers access auditqueue.qlen via skbqueue_len() without holding the queue lock or using READ_ONCE(), while kauditd writes to this field via the skbdequeue() →…
When was CVE-2026-64435 disclosed?
CVE-2026-64435 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64435 actively exploited?
CVE-2026-64435 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 73.5% of all scored CVEs.
What is the CVSS score of CVE-2026-64435?
CVE-2026-64435 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-64435?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64435, 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-64435

Explore →

Is Your Infrastructure Affected by CVE-2026-64435?

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