Linux: Use After Free
CVE-2026-53156 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 6cdcf0d16c80900f42d60252480cd131c1a83d23, e0d38bf47a72da2f02c9fa6f752cd66d977cd7f7, cb85ef5a227b3662b88f4d849a1aad43bfe7f5ae 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.13% 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 6cdcf0d16c80900f42d60252480cd131c1a83d23 or e0d38bf47a72da2f02c9fa6f752cd66d977cd7f7 or cb85ef5a227b3662b88f4d849a1aad43bfe7f5ae or 40e2a459c0dd1333b2343831480a0ad80dc07614, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.12.94 or 6.18.36 or 7.0.13, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | e888d445ac33a5b0288d670ecd970908b13f07cd up to, but not including, 6cdcf0d16c80900f42d60252480cd131c1a83d23; e888d445ac33a5b0288d670ecd970908b13f07cd up to, but not including, e0d38bf47a72da2f02c9fa6f752cd66d977cd7f7; e888d445ac33a5b0288d670ecd970908b13f07cd up to, but not including, cb85ef5a227b3662b88f4d849a1aad43bfe7f5ae; e888d445ac33a5b0288d670ecd970908b13f07cd up to, but not including, 40e2a459c0dd1333b2343831480a0ad80dc07614; e888d445ac33a5b0288d670ecd970908b13f07cd up to, but not including, 5b6b6fc491899d583eaa75344e094796ae9b530b; 4.20 | 6cdcf0d16c80900f42d60252480cd131c1a83d23, e0d38bf47a72da2f02c9fa6f752cd66d977cd7f7, cb85ef5a227b3662b88f4d849a1aad43bfe7f5ae, 40e2a459c0dd1333b2343831480a0ad80dc07614, 5b6b6fc491899d583eaa75344e094796ae9b530b |
| Linux | Linux Kernel | 4.20 up to, but not including, 6.12.94; 6.13 up to, but not including, 6.18.36; 6.19 up to, but not including, 7.0.13; 7.1 | 6.12.94, 6.18.36, 7.0.13 |
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: nvmem: core: fix use-after-free bugs in error paths Fix several instances of error paths in which we call __nvmem_device_put() - which may end up freeing the underlying memory and other resources - and then keep on using the nvmem structure. Always put the reference to the nvmem device as the last step before returning the error code.
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: partial).
- 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
- 9.8 Critical severity
- 7.8 High severity
- 7.8 High severity
- 7.5 High severity
- 8.2 High severity
Spotted an error? Tell us.