CVE-2026-53240
Last modified
CVE-2026-53240 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: xfrm: iptfs: fix use-after-free on first_skb in __input_process_payload __input_process_payload() stores first_skb into xtfs->ra_newskb under drop_lock when starting partial reassembly, then unlocks and breaks out of the processing loop. The post-loop check reads xtfs->ra_newskb without the lock to decide whether first_skb is still owned: if (first_skb && first_iplen && !defer && first_skb != xtfs->ra_newskb) Between spin_unlock and this read, a concurrent CPU running iptfs_reassem_cont() (or the drop_timer hrtimer) can complete reassembly, NULL xtfs->ra_newskb, and free the skb. EPSS estimates a 0.42% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: xfrm: iptfs: fix use-after-free on first_skb in __input_process_payload __input_process_payload() stores first_skb into xtfs->ra_newskb under drop_lock when starting partial reassembly, then unlocks and breaks out of the processing loop. The post-loop check reads xtfs->ra_newskb without the lock to decide whether first_skb is still owned: if (first_skb && first_iplen && !defer && first_skb != xtfs->ra_newskb) Between spin_unlock and this read, a concurrent CPU running iptfs_reassem_cont() (or the drop_timer hrtimer) can complete reassembly, NULL xtfs->ra_newskb, and free the skb. The check then evaluates first_skb != NULL as true, and pskb_trim/ip_summed/consume_skb operate on the freed skb — a use-after-free in skbuff_head_cache. Replace the unlocked read with a local bool that records whether first_skb was handed to the reassembly state in the current call. The flag is set after the existing spin_unlock, before the break, using the pointer equality that is stable at that point (first_skb == skb iff first_skb was stored in ra_newskb).
Metrics
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.14, < 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-53240?
How severe is CVE-2026-53240?
How do I fix CVE-2026-53240?
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-53235In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53236In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53237In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53238In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53239In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-5324The Brizy – Page Builder plugin for WordPress is vulnerable …7.2
- CVE-2026-53241In the Linux kernel, the following vulnerability has been re…5.5
- 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
Are you affected by CVE-2026-53240?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
