Linux: Use After Free
CVE-2026-53115 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 dbba371b19129abe9649553ab912e6bccf6c1a5b, 4911b836f35c034c36f102db4ecbe339b38e7d1d, 8139ce66b52a4a5638bfb445b037c07d4abeb08e 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.18% 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 dbba371b19129abe9649553ab912e6bccf6c1a5b or 4911b836f35c034c36f102db4ecbe339b38e7d1d or 8139ce66b52a4a5638bfb445b037c07d4abeb08e or 60bfb563a399c4597dc80588a1109758a8908b97, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.12.91 or 6.18.33 or 7.0.10, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d up to, but not including, dbba371b19129abe9649553ab912e6bccf6c1a5b; 1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d up to, but not including, 4911b836f35c034c36f102db4ecbe339b38e7d1d; 1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d up to, but not including, 8139ce66b52a4a5638bfb445b037c07d4abeb08e; 1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d up to, but not including, 60bfb563a399c4597dc80588a1109758a8908b97; 1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d up to, but not including, 6c8dfb0362732bf1e4829867a2a5239fedc592d0; 5.10 | dbba371b19129abe9649553ab912e6bccf6c1a5b, 4911b836f35c034c36f102db4ecbe339b38e7d1d, 8139ce66b52a4a5638bfb445b037c07d4abeb08e, 60bfb563a399c4597dc80588a1109758a8908b97, 6c8dfb0362732bf1e4829867a2a5239fedc592d0 |
| Linux | Linux Kernel | 5.10 up to, but not including, 6.12.91; 6.13 up to, but not including, 6.18.33; 6.19 up to, but not including, 7.0.10 | 6.12.91, 6.18.33, 7.0.10 |
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.
Official description
In the Linux kernel, the following vulnerability has been resolved: bus: fsl-mc: use generic driver_override infrastructure When a driver is probed through __driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can cause a UAF. Fix this by using the driver-core driver_override infrastructure taking care of proper locking internally. Note that calling match() from __driver_attach() without the device lock held is intentional. [1]
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.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
Recent Use After Free vulnerabilities
- 7.5 High severity
- 8.8 High severity
- 7.8 High severity
- 8.8 High severity
- 8.8 High severity
- 9.6 Critical severity
Spotted an error? Tell us.