CVE-2026-53240: xfrm: iptfs: fix use-after-free on first_skb in __input_process_payload

Published Jun 25, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

xfrm: iptfs: fix use-after-free on firstskb in inputprocesspayload

inputprocesspayload() stores firstskb into xtfs->ranewskb under droplock when starting partial reassembly, then unlocks and breaks out of the processing loop. The post-loop check reads xtfs->ranewskb without the lock to decide whether firstskb is still owned:

if (firstskb && firstiplen && !defer && firstskb != xtfs->ranewskb)

Between spinunlock and this read, a concurrent CPU running iptfsreassemcont() (or the droptimer hrtimer) can complete reassembly, NULL xtfs->ranewskb, and free the skb. The check then evaluates firstskb != NULL as true, and pskbtrim/ipsummed/consumeskb operate on the freed skb — a use-after-free in skbuffheadcache.

Replace the unlocked read with a local bool that records whether firstskb was handed to the reassembly state in the current call. The flag is set after the existing spinunlock, before the break, using the pointer equality that is stable at that point (firstskb == skb iff firstskb was stored in ranewskb).

Affected Software

10 affected components
Linux Linux kernel
Linux Linux kernel>=6.14<6.18.36
Linux Linux kernel>=6.19<7.0.13
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2
Linux Linux kernel=7.1-rc3
Linux Linux kernel=7.1-rc4
Linux Linux kernel=7.1-rc5
Linux Linux kernel=7.1-rc6
Linux Linux kernel=7.1-rc7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux kernel xfrm: iptfs to a version that resolves this vulnerability.

    Patch xfrm: iptfs: fix use-after-free on first_skb in __input_process_payload

Event History

Jun 25, 2026
CVE Published
via MITRE·08:39 AM
Data Sourced
via MITRE·08:39 AM
DescriptionSeverity
Data Sourced
via NVD·09:16 AM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-53240?

The severity of CVE-2026-53240 is rated at risk 47.

2

What type of vulnerability is CVE-2026-53240?

CVE-2026-53240 is categorized as a Use After Free vulnerability.

3

How does CVE-2026-53240 affect the Linux kernel?

CVE-2026-53240 affects the Linux kernel by creating a use-after-free condition in the __input_process_payload function.

4

How do I fix CVE-2026-53240?

To fix CVE-2026-53240, apply the latest patch provided in the Linux kernel updates.

5

When was CVE-2026-53240 published?

CVE-2026-53240 was published on June 25, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203