Linux: Use After Free
CVE-2026-53248 is a high-severity use after free vulnerability in Linux, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists versions 6f829e2c17a53a35321268339cd252aff6d6d723, 4b5a574e033e66d2131eff1c18feef8d8643c67e, b38cae85d1c45ff189d7ecb6ac36f41cdc3d84d0 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.53% 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 6f829e2c17a53a35321268339cd252aff6d6d723 or 4b5a574e033e66d2131eff1c18feef8d8643c67e or b38cae85d1c45ff189d7ecb6ac36f41cdc3d84d0, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.18.36 or 7.0.13, whichever matches your release line, or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | af3cf757d5c99011b9b94ea8d78aeaccc0153fdc up to, but not including, 6f829e2c17a53a35321268339cd252aff6d6d723; af3cf757d5c99011b9b94ea8d78aeaccc0153fdc up to, but not including, 4b5a574e033e66d2131eff1c18feef8d8643c67e; af3cf757d5c99011b9b94ea8d78aeaccc0153fdc up to, but not including, b38cae85d1c45ff189d7ecb6ac36f41cdc3d84d0; 6.15 | 6f829e2c17a53a35321268339cd252aff6d6d723, 4b5a574e033e66d2131eff1c18feef8d8643c67e, b38cae85d1c45ff189d7ecb6ac36f41cdc3d84d0 |
| Linux | Linux Kernel | 6.15 up to, but not including, 6.18.36; 6.19 up to, but not including, 7.0.13; 7.1 | 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
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- 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:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by CNA.
Official description
In the Linux kernel, the following vulnerability has been resolved: net: airoha: Fix use-after-free in metadata dst teardown airoha_metadata_dst_free() runs metadata_dst_free() which frees the metadata_dst with kfree() immediately, bypassing the RCU grace period. In the RX path, skb_dst_set_noref() sets a non-refcounted pointer from the skb to the metadata_dst. This function requires RCU read-side protection and the dst must remain valid until all RCU readers complete. Since metadata_dst_free() calls kfree() directly, an use-after-free can occur if any skb still holds a noref pointer to the dst when the driver tears it down. Replace metadata_dst_free() with dst_release() which properly goes through the refcount path: when the refcount drops to zero, it schedules the actual free via call_rcu_hurry(), ensuring all RCU readers have completed before the memory is freed.
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
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.