Skip to main content
VulnerabilityPublished Updated

CVE-2026-64435: Linux kernel · Race Condition

Source GCVE Database

0
Authoritative record:CVE-2026-64435· High 8.2

Not known to be exploited · CVSS 8.2 High · fixed in fe997a84a385f840b593ead92e575503a5046cee : patch Linux kernel soon.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in fe997a84a385f840b593ead92e575503a5046cee, e575dabb805252e3113fdc3f56f6ecacfde422d0, c5186201fa7030289cc4fe23fae87a3fcb566856 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 3197542482df22c2a131d4a813280bd7c54cedf5, < fe997a84a385f840b593ead92e575503a5046cee
Fixed in
  • fe997a84a385f840b593ead92e575503a5046cee
LinuxLinuxAffected
  • ≥ 3197542482df22c2a131d4a813280bd7c54cedf5, < e575dabb805252e3113fdc3f56f6ecacfde422d0
Fixed in
  • e575dabb805252e3113fdc3f56f6ecacfde422d0
LinuxLinuxAffected
  • ≥ 3197542482df22c2a131d4a813280bd7c54cedf5, < c5186201fa7030289cc4fe23fae87a3fcb566856
Fixed in
  • c5186201fa7030289cc4fe23fae87a3fcb566856
LinuxLinuxAffected
  • ≥ 3197542482df22c2a131d4a813280bd7c54cedf5, < c9a71daaecb2fb1d8c704545cc0b1c920b9bf5d7
Fixed in
  • c9a71daaecb2fb1d8c704545cc0b1c920b9bf5d7
LinuxLinuxAffected
  • ≥ 3197542482df22c2a131d4a813280bd7c54cedf5, < b35597bdae1a5d8395da4b9baa993b9b71f74d68
Fixed in
  • b35597bdae1a5d8395da4b9baa993b9b71f74d68
LinuxLinuxAffected
  • ≥ 3197542482df22c2a131d4a813280bd7c54cedf5, < a3d85dec60bb0622360fc176b2a51abdbe2ff0ad
Fixed in
  • a3d85dec60bb0622360fc176b2a51abdbe2ff0ad

AI-suggested

A fix is available that replaces the vulnerable skb_queue_len() calls with skb_queue_len_lockless(), which uses atomic operations to prevent data races. Users should update to a Linux kernel version that includes this fix. Since this is a kernel-level fix, applying the official kernel update is the recommended remediation.

Description

A data race vulnerability in the Linux kernel's audit subsystem was resolved by replacing unsafe access to audit_queue length with a lockless helper that uses proper atomic operations. The flaw involved multiple readers accessing audit_queue.qlen without proper synchronization, while a writer updated it under a spinlock, leading to potential data races. This issue was reported by KCSAN and affects audit_queue length reads in several audit-related functions.

References

Community reviews

Loading reviews…