Linux: Improper Locking
CVE-2026-64068 is a critical-severity improper locking vulnerability in Linux, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions f59c4ec86ef3a9ac99706ae163a38ec28129fd76, d5c9d19b0ff2f7153532ac238a5e96fed2df315c, 393f3f0d7353a94b1e0bc4ca89c683fe983e5fd2 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.35% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Linux to f59c4ec86ef3a9ac99706ae163a38ec28129fd76 or d5c9d19b0ff2f7153532ac238a5e96fed2df315c or 393f3f0d7353a94b1e0bc4ca89c683fe983e5fd2 or cce18c263e9623872327ba3c956012f73c1179cc, whichever matches your release line, or a later version.
- Update Linux Kernel to 7.0.11 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 288ace2f57c9d06dd2e42bd80d03747d879a4068 up to, but not including, f59c4ec86ef3a9ac99706ae163a38ec28129fd76; 288ace2f57c9d06dd2e42bd80d03747d879a4068 up to, but not including, d5c9d19b0ff2f7153532ac238a5e96fed2df315c; 288ace2f57c9d06dd2e42bd80d03747d879a4068 up to, but not including, 393f3f0d7353a94b1e0bc4ca89c683fe983e5fd2; 288ace2f57c9d06dd2e42bd80d03747d879a4068 up to, but not including, cce18c263e9623872327ba3c956012f73c1179cc; 6.10 | f59c4ec86ef3a9ac99706ae163a38ec28129fd76, d5c9d19b0ff2f7153532ac238a5e96fed2df315c, 393f3f0d7353a94b1e0bc4ca89c683fe983e5fd2, cce18c263e9623872327ba3c956012f73c1179cc |
| Linux | Linux Kernel | 6.10 up to, but not including, 7.0.11; 7.1 | 7.0.11 |
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
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- 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:N/AC:L/PR:N/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: netfs: Fix missing locking around retry adding new subreqs Fix netfs_retry_read_subrequests() and netfs_retry_write_stream() to take the appropriate lock when adding extra subrequests into stream->subrequests.
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.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
Recent Improper Locking vulnerabilities
- 7.8 High severity
- 9.8 Critical severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 8.8 High severity
Spotted an error? Tell us.