Linux: Improper Locking
CVE-2026-46112 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 1f0a3aa8b569d010316b427238222c5d899f9618, b6296ff2475fc95ee6ea1b528c4b385302808186, fb4ae739811d467409bd07d0e36cfd4140f3d26a 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 1f0a3aa8b569d010316b427238222c5d899f9618 or b6296ff2475fc95ee6ea1b528c4b385302808186 or fb4ae739811d467409bd07d0e36cfd4140f3d26a or fcf6a832c0d5b2bc5398d6996c5570d3ee7993fb, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.15.209 or 6.1.175 or 6.6.140 or 6.12.88, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | e088a685eae94a0607b8f7b99949a0e14d748813 up to, but not including, 1f0a3aa8b569d010316b427238222c5d899f9618; e088a685eae94a0607b8f7b99949a0e14d748813 up to, but not including, b6296ff2475fc95ee6ea1b528c4b385302808186; e088a685eae94a0607b8f7b99949a0e14d748813 up to, but not including, fb4ae739811d467409bd07d0e36cfd4140f3d26a; e088a685eae94a0607b8f7b99949a0e14d748813 up to, but not including, fcf6a832c0d5b2bc5398d6996c5570d3ee7993fb; e088a685eae94a0607b8f7b99949a0e14d748813 up to, but not including, 1912f78798505dc9c637081bbddfbf1c22494c49; e088a685eae94a0607b8f7b99949a0e14d748813 up to, but not including, 615d9d260c32bb678504ca96f29ae46f9d745155; e088a685eae94a0607b8f7b99949a0e14d748813 up to, but not including, 0c99acbc8b6c6dd526ae475a48ee1897b61072fb; 4.17 | 1f0a3aa8b569d010316b427238222c5d899f9618, b6296ff2475fc95ee6ea1b528c4b385302808186, fb4ae739811d467409bd07d0e36cfd4140f3d26a, fcf6a832c0d5b2bc5398d6996c5570d3ee7993fb, 1912f78798505dc9c637081bbddfbf1c22494c49, 615d9d260c32bb678504ca96f29ae46f9d745155 |
| Linux | Linux Kernel | 4.17 up to, but not including, 5.15.209; 5.16 up to, but not including, 6.1.175; 6.2 up to, but not including, 6.6.140; 6.7 up to, but not including, 6.12.88; 6.13 up to, but not including, 6.18.30; 6.19 up to, but not including, 7.0.7; 7.1 | 5.15.209, 6.1.175, 6.6.140, 6.12.88, 6.18.30, 7.0.7 |
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: RDMA/hns: Fix unlocked call to hns_roce_qp_remove() Sashiko points out that hns_roce_qp_remove() requires the caller to hold locks. The error flow in hns_roce_create_qp_common() doesn't hold those locks for the error unwind so it risks corrupting memory. Grab the same locks the other two callers use.
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
- git.kernel.org/stable/c/0c99acbc8b6c6dd526ae475a48ee1897b61072fb
- git.kernel.org/stable/c/1912f78798505dc9c637081bbddfbf1c22494c49
- git.kernel.org/stable/c/1f0a3aa8b569d010316b427238222c5d899f9618
- git.kernel.org/stable/c/615d9d260c32bb678504ca96f29ae46f9d745155
- git.kernel.org/stable/c/b6296ff2475fc95ee6ea1b528c4b385302808186
- git.kernel.org/stable/c/fb4ae739811d467409bd07d0e36cfd4140f3d26a
- git.kernel.org/stable/c/fcf6a832c0d5b2bc5398d6996c5570d3ee7993fb
Recent Improper Locking vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
- 7.8 High severity
Spotted an error? Tell us.