CVE-2026-99775: xfrm: interface: validate the IP header on xmit

Published Nov 20, 2026
·
Updated

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

xfrm: interface: validate the IP header on xmit

Packets injected into an xfrm interface (e.g. AFPACKET on an xfrmi device) reach the xfrm output path without IP header validation, but xfrm4transportoutput() uses iph->ihl for skbpull() and memmove() and expects the header to be valid.

vtitunnelxmit() already calls pskbinetmaypull() before handing packets to the xfrm output path. Do the same in xfrmixmit() and perform the header checks iprcvcore()/ip6rcvcore() do on entry to the IP stack: reject wrong IP versions and malformed IPv4 header lengths.

Affected Software

7 affected componentsFixes available
linux/kernel>=4.19.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux*
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1, <=6.12.117-1, <=7.3.4-1
7.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:51 AM
Data Sourced
via MITRE·05:51 AM
Description
Data Sourced
via OSV·05:51 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

Which deployments are most relevant to this issue?

Systems using xfrm interfaces are the relevant exposure area, particularly where packets can be injected into an xfrmi device, such as through AF_PACKET.

2

What does a malformed packet need to contain to reach the vulnerable handling?

The packet must reach the xfrm output path through an xfrm interface with an invalid IP header. The fix rejects incorrect IP versions and malformed IPv4 header lengths before xfrm output processing.

3

Are specific affected kernel versions identified?

No affected version ranges are provided in the available data. Three stable-kernel commit references are listed as fixes.

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