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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
35%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 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.

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.12—6.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 (156 versions)7.1.4-1—

Data Freshness Timeline

(refreshed 28× in last 7d / 153× 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 185 total refreshes for this CVE.

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

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 August 17, 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 64.7% 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.

Start Free Scan →Browse All CVEs