Linux: Use After Free
CVE-2026-31511 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 2074dfffad76981ca451cb7fc98703d04ac562fe, 340666172cf747de58c283d2eef1f335f050538b, bafec9325d4de26b6c49db75b5d5172de652aae0 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 2074dfffad76981ca451cb7fc98703d04ac562fe or 340666172cf747de58c283d2eef1f335f050538b or bafec9325d4de26b6c49db75b5d5172de652aae0 or 3a89c33deffb3cb7877a7ea2e50734cd12b064f2, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.12.80 or 6.17 or 6.18.21 or 6.19.11, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 0b60eb04b8524e1b4b3f07fea0d16fda9a677d9a up to, but not including, 2074dfffad76981ca451cb7fc98703d04ac562fe; d71b98f253b079cbadc83266383f26fe7e9e103b up to, but not including, 340666172cf747de58c283d2eef1f335f050538b; 302a1f674c00dd5581ab8e493ef44767c5101aab up to, but not including, bafec9325d4de26b6c49db75b5d5172de652aae0; 302a1f674c00dd5581ab8e493ef44767c5101aab up to, but not including, 3a89c33deffb3cb7877a7ea2e50734cd12b064f2; 302a1f674c00dd5581ab8e493ef44767c5101aab up to, but not including, 5f5fa4cd35f707344f65ce9e225b6528691dbbaa; 87a1f16f07c6c43771754075e08f45b41d237421; 6.12.59 up to, but not including, 6.12.80; 6.16.10 up to, but not including, 6.17; and 1 more ranges | 2074dfffad76981ca451cb7fc98703d04ac562fe, 340666172cf747de58c283d2eef1f335f050538b, bafec9325d4de26b6c49db75b5d5172de652aae0, 3a89c33deffb3cb7877a7ea2e50734cd12b064f2, 5f5fa4cd35f707344f65ce9e225b6528691dbbaa, 6.12.80 |
| Linux | Linux Kernel | 6.12.59 up to, but not including, 6.12.80; 6.16.10 up to, but not including, 6.17; 6.17.1 up to, but not including, 6.18.21; 6.19 up to, but not including, 6.19.11; 6.17; 7.0 | 6.12.80, 6.17, 6.18.21, 6.19.11 |
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 CNA.
Official description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete This fixes the condition checking so mgmt_pending_valid is executed whenever status != -ECANCELED otherwise calling mgmt_pending_free(cmd) would kfree(cmd) without unlinking it from the list first, leaving a dangling pointer. Any subsequent list traversal (e.g., mgmt_pending_foreach during __mgmt_power_off, or another mgmt_pending_valid call) would dereference freed memory.
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
Other references
Recent Use After Free vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.