Linux: Use After Free
CVE-2026-23013 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 aa05a8371ae4a452df623f7202c72409d3c50e40, aa4c066229b05fc3d3c5f42693d25b1828533b6e, f93fc5d12d69012788f82151bee55fce937e1432 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.19% 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 aa05a8371ae4a452df623f7202c72409d3c50e40 or aa4c066229b05fc3d3c5f42693d25b1828533b6e or f93fc5d12d69012788f82151bee55fce937e1432, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.12.67 or 6.18.7, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 1cd3b407977c3ab1d2ddc26cb7113e7fb1509cd1 up to, but not including, aa05a8371ae4a452df623f7202c72409d3c50e40; 1cd3b407977c3ab1d2ddc26cb7113e7fb1509cd1 up to, but not including, aa4c066229b05fc3d3c5f42693d25b1828533b6e; 1cd3b407977c3ab1d2ddc26cb7113e7fb1509cd1 up to, but not including, f93fc5d12d69012788f82151bee55fce937e1432; 6.9 | aa05a8371ae4a452df623f7202c72409d3c50e40, aa4c066229b05fc3d3c5f42693d25b1828533b6e, f93fc5d12d69012788f82151bee55fce937e1432 |
| Linux | Linux Kernel | 6.9.1 up to, but not including, 6.12.67; 6.13 up to, but not including, 6.18.7; 6.9; 6.19 | 6.12.67, 6.18.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 NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.0 | High | CNA |
| CVSS 3.1 | 7.8 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: net: octeon_ep_vf: fix free_irq dev_id mismatch in IRQ rollback octep_vf_request_irqs() requests MSI-X queue IRQs with dev_id set to ioq_vector. If request_irq() fails part-way, the rollback loop calls free_irq() with dev_id set to 'oct', which does not match the original dev_id and may leave the irqaction registered. This can keep IRQ handlers alive while ioq_vector is later freed during unwind/teardown, leading to a use-after-free or crash when an interrupt fires. Fix the error path to free IRQs with the same ioq_vector dev_id used during request_irq().
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
Recent Use After Free vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.8 High severity
Spotted an error? Tell us.