CVE-2026-99774: xfrm: espintcp: reorder operations within espintcp_init_sk

Published Nov 20, 2026
·
Updated

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

xfrm: espintcp: reorder operations within espintcpinitsk

When enabled on a socket, espintcp sets the socket callbacks to its own before it has finished setting up its context and published it as icskulpdata. Any one of those callbacks that gets called before will dereference a NULL icskulpdata.

Fix this by reording the operations, and add memory barriers to ensure callers will have a struct espintcpctx available. Add a few WRITEONCE/READONCE too while we're there.

Affected Software

3 affected componentsFixes available
linux/kernel>=5.6.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

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. Compensating control

    In Linux kernel xfrm ESP-in-TCP (espintcp), reorder operations in espintcp_init_sk so the socket callbacks are not published before the context is initialized; add memory barriers and use WRITE_ONCE/READ_ONCE when accessing icsk_ulp_data.

Frequently Asked Questions

1

Which systems are exposed to this issue?

Linux kernel systems where ESP-in-TCP is enabled on a socket are exposed. The issue occurs during ESP-in-TCP socket initialization, when callbacks can run before the socket context has been published.

2

What condition triggers the vulnerability?

A socket callback must be invoked in the interval after espintcp replaces the socket callbacks but before its context is available through icsk_ulp_data. That callback can dereference a NULL icsk_ulp_data value.

3

What is the remediation?

Apply a kernel update containing the fix that reorders ESP-in-TCP initialization and adds memory-ordering and READ_ONCE/WRITE_ONCE protections. The provided references identify stable kernel commits containing the correction.

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