CVE-2026-53248
Last modified
CVE-2026-53248 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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.. EPSS estimates a 0.39% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.15, < 6.18.36 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.13 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53248?
How severe is CVE-2026-53248?
How do I fix CVE-2026-53248?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53242In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53243In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53244In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53245In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53246In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53247In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53249In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-5325A vulnerability was determined in SourceCodester Simple Cust…3.5
- CVE-2026-53250In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53251In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53252In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53253In the Linux kernel, the following vulnerability has been re…7.1
Are you affected by CVE-2026-53248?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
