Linux: Use After Free
CVE-2024-50051 is a high-severity use after free 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 d0cde3911cf24e1bcdd4caa1d1b9ef57589db5a1, e0c6ce8424095c2da32a063d3fc027494c689817, cd5106c77d6d6828aa82449f01f4eb436d602a21 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.26% 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 d0cde3911cf24e1bcdd4caa1d1b9ef57589db5a1 or e0c6ce8424095c2da32a063d3fc027494c689817 or cd5106c77d6d6828aa82449f01f4eb436d602a21 or 373d55a47dc662e5e30d12ad5d334312f757c1f1, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.4.287 or 5.10.231 or 5.15.174 or 6.1.120, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | ca632f556697d45d67ed5cada7cedf3ddfe0db4b up to, but not including, d0cde3911cf24e1bcdd4caa1d1b9ef57589db5a1; ca632f556697d45d67ed5cada7cedf3ddfe0db4b up to, but not including, e0c6ce8424095c2da32a063d3fc027494c689817; ca632f556697d45d67ed5cada7cedf3ddfe0db4b up to, but not including, cd5106c77d6d6828aa82449f01f4eb436d602a21; ca632f556697d45d67ed5cada7cedf3ddfe0db4b up to, but not including, 373d55a47dc662e5e30d12ad5d334312f757c1f1; ca632f556697d45d67ed5cada7cedf3ddfe0db4b up to, but not including, f65d85bc1ffd8a2c194bb2cd65e35ed3648ddd59; ca632f556697d45d67ed5cada7cedf3ddfe0db4b up to, but not including, 90b72189de2cddacb26250579da0510b29a8b82b; ca632f556697d45d67ed5cada7cedf3ddfe0db4b up to, but not including, 984836621aad98802d92c4a3047114cf518074c8; 3.1 | d0cde3911cf24e1bcdd4caa1d1b9ef57589db5a1, e0c6ce8424095c2da32a063d3fc027494c689817, cd5106c77d6d6828aa82449f01f4eb436d602a21, 373d55a47dc662e5e30d12ad5d334312f757c1f1, f65d85bc1ffd8a2c194bb2cd65e35ed3648ddd59, 90b72189de2cddacb26250579da0510b29a8b82b |
| Linux | Linux Kernel | 3.1 up to, but not including, 5.4.287; 5.5 up to, but not including, 5.10.231; 5.11 up to, but not including, 5.15.174; 5.16 up to, but not including, 6.1.120; 6.2 up to, but not including, 6.6.66; 6.7 up to, but not including, 6.12.5; 6.13 | 5.4.287, 5.10.231, 5.15.174, 6.1.120, 6.6.66, 6.12.5 |
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 | NVD |
| CVSS 3.1 | 7.8 | High | CISA (ADP) |
Official description
In the Linux kernel, the following vulnerability has been resolved: spi: mpc52xx: Add cancel_work_sync before module remove If we remove the module which will call mpc52xx_spi_remove it will free 'ms' through spi_unregister_controller. while the work ms->work will be used. The sequence of operations that may lead to a UAF bug. Fix it by ensuring that the work is canceled before proceeding with the cleanup in mpc52xx_spi_remove.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.
How developers prevent this class of flaw
- Choose a language that provides automatic memory management.
- When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
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/373d55a47dc662e5e30d12ad5d334312f757c1f1
- git.kernel.org/stable/c/90b72189de2cddacb26250579da0510b29a8b82b
- git.kernel.org/stable/c/984836621aad98802d92c4a3047114cf518074c8
- git.kernel.org/stable/c/cd5106c77d6d6828aa82449f01f4eb436d602a21
- git.kernel.org/stable/c/d0cde3911cf24e1bcdd4caa1d1b9ef57589db5a1
- git.kernel.org/stable/c/e0c6ce8424095c2da32a063d3fc027494c689817
- git.kernel.org/stable/c/f65d85bc1ffd8a2c194bb2cd65e35ed3648ddd59
Other references
Recent Use After Free vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.