Linux: Improper Locking
CVE-2022-50518 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 04a603058e70b8b881bb7860b8bd649f931f2591, 553bc5890ed96a8d006224c3a4673c47fee0d12a, 7236aae5f81f3efbd93d0601e74fc05994bc2580 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.14% 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 04a603058e70b8b881bb7860b8bd649f931f2591 or 553bc5890ed96a8d006224c3a4673c47fee0d12a or 7236aae5f81f3efbd93d0601e74fc05994bc2580 or 2.6.25, whichever matches your release line, or a later version.
- Update Linux Kernel to 2.6.25 or 6.0.18 or 6.1.4, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | ef1afd4d79f0479960ff36bb5fe6ec6eba1ebff2 up to, but not including, 04a603058e70b8b881bb7860b8bd649f931f2591; ef1afd4d79f0479960ff36bb5fe6ec6eba1ebff2 up to, but not including, 553bc5890ed96a8d006224c3a4673c47fee0d12a; ef1afd4d79f0479960ff36bb5fe6ec6eba1ebff2 up to, but not including, 7236aae5f81f3efbd93d0601e74fc05994bc2580; 24319896af06b84f965bcefa0f2d926b726ed05b; 2.6.24.5 up to, but not including, 2.6.25; 2.6.25 | 04a603058e70b8b881bb7860b8bd649f931f2591, 553bc5890ed96a8d006224c3a4673c47fee0d12a, 7236aae5f81f3efbd93d0601e74fc05994bc2580, 2.6.25 |
| Linux | Linux Kernel | 2.6.24.5 up to, but not including, 2.6.25; 2.6.25.1 up to, but not including, 6.0.18; 6.1 up to, but not including, 6.1.4; 2.6.25 | 2.6.25, 6.0.18, 6.1.4 |
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 NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: parisc: Fix locking in pdc_iodc_print() firmware call Utilize pdc_lock spinlock to protect parallel modifications of the iodc_dbuf[] buffer, check length to prevent buffer overflow of iodc_dbuf[], drop the iodc_retbuf[] buffer and fix some wrong indentings.
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
Recent Improper Locking vulnerabilities
- 8.1 High severity
- 7.5 High severity
- 7.8 High severity
- 7.8 High severity
- 7.1 High severity
- 7.5 High severity
Spotted an error? Tell us.