Linux: Improper Locking
CVE-2026-64005 is a high-severity improper locking vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions cdc79c05cc375f68ae87b0c74fdaac1a5c93155a, 2006605006e5a4a11d93e1ebdbbe95764d24276f, 64c96e497d5ada0b90e99bf58f893aa2b73dcfbc as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.1% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to cdc79c05cc375f68ae87b0c74fdaac1a5c93155a or 2006605006e5a4a11d93e1ebdbbe95764d24276f or 64c96e497d5ada0b90e99bf58f893aa2b73dcfbc or ed7a758313011885347b854e97cb95903ef3c3f7, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.10.259 or 5.15.210 or 6.1.176 or 6.6.143, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | f16a7dd5cf27eeda187425c9c7d96802a549f9c4 up to, but not including, cdc79c05cc375f68ae87b0c74fdaac1a5c93155a; f16a7dd5cf27eeda187425c9c7d96802a549f9c4 up to, but not including, 2006605006e5a4a11d93e1ebdbbe95764d24276f; f16a7dd5cf27eeda187425c9c7d96802a549f9c4 up to, but not including, 64c96e497d5ada0b90e99bf58f893aa2b73dcfbc; f16a7dd5cf27eeda187425c9c7d96802a549f9c4 up to, but not including, ed7a758313011885347b854e97cb95903ef3c3f7; f16a7dd5cf27eeda187425c9c7d96802a549f9c4 up to, but not including, 0cc9d0ac22d02f1ba1884de5d6de9eaf8b45d82d; f16a7dd5cf27eeda187425c9c7d96802a549f9c4 up to, but not including, 55cba6b883b41e5922c00ba9d4e3262131f46f1b; f16a7dd5cf27eeda187425c9c7d96802a549f9c4 up to, but not including, 5ec939367e700722ffbb1b7cacccbb1a3cf0ebd1; f16a7dd5cf27eeda187425c9c7d96802a549f9c4 up to, but not including, 9e4389b0038781f19f97895186ed941ff8ac1678; and 1 more ranges | cdc79c05cc375f68ae87b0c74fdaac1a5c93155a, 2006605006e5a4a11d93e1ebdbbe95764d24276f, 64c96e497d5ada0b90e99bf58f893aa2b73dcfbc, ed7a758313011885347b854e97cb95903ef3c3f7, 0cc9d0ac22d02f1ba1884de5d6de9eaf8b45d82d, 55cba6b883b41e5922c00ba9d4e3262131f46f1b |
| Linux | Linux Kernel | 4.11 up to, but not including, 5.10.259; 5.11 up to, but not including, 5.15.210; 5.16 up to, but not including, 6.1.176; 6.2 up to, but not including, 6.6.143; 6.7 up to, but not including, 6.12.93; 6.13 up to, but not including, 6.18.35; 6.19 up to, but not including, 7.0.12; 7.1 | 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93, 6.18.35 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.
Official description
In the Linux kernel, the following vulnerability has been resolved: net/smc: Do not re-initialize smc hashtables INIT_HLIST_HEAD(&smc_v*_hashinfo.ht) are called after smc_nl_init(), proto_register() and sock_register(). This can lead to smc_v*_hashinfo.ht being reset even though hash entries already exist and are being used, possibly resulting in a corrupted list. Remove unnecessary and dangerous re-initialisation of smc_v*_hashinfo.ht in smc_init(); it is implicitly initialised to zero anyhow. Add HLIST_HEAD_INIT to the definitions for clarity.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Locking
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
How developers prevent this class of flaw
- Use industry standard APIs to implement locking mechanism.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/0cc9d0ac22d02f1ba1884de5d6de9eaf8b45d82d
- git.kernel.org/stable/c/2006605006e5a4a11d93e1ebdbbe95764d24276f
- git.kernel.org/stable/c/55cba6b883b41e5922c00ba9d4e3262131f46f1b
- git.kernel.org/stable/c/5ec939367e700722ffbb1b7cacccbb1a3cf0ebd1
- git.kernel.org/stable/c/64c96e497d5ada0b90e99bf58f893aa2b73dcfbc
- git.kernel.org/stable/c/9e4389b0038781f19f97895186ed941ff8ac1678
- git.kernel.org/stable/c/cdc79c05cc375f68ae87b0c74fdaac1a5c93155a
- git.kernel.org/stable/c/ed7a758313011885347b854e97cb95903ef3c3f7
Recent Improper Locking vulnerabilities
- 7.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.8 High severity
- 7.8 High severity
- 8.8 High severity
Spotted an error? Tell us.