CVE-2026-53250: xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata()

Published Jun 25, 2026
·
Updated

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

xsk: cache csumstart/csumoffset to fix TOCTOU in xskskbmetadata()

The TX metadata area resides in the UMEM buffer which is memory-mapped and concurrently writable by userspace. In xskskbmetadata(), csumstart and csumoffset are read from shared memory for bounds validation, then read again for skb assignment. A malicious userspace application can race to overwrite these values between the two reads, bypassing the bounds check and causing out-of-bounds memory access during checksum computation in the transmit path.

Fix this by reading csumstart and csumoffset into local variables once, then using the local copies for both validation and assignment.

Note that other metadata fields (flags, launchtime) and the cached csum fields may be mutually inconsistent due to concurrent userspace writes, but this is benign: the only security-critical invariant is that each field's validated value is the same one used, which local caching guarantees.

Affected Software

9 affected components
Linux Linux kernel
Linux Linux kernel>=6.8<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

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    In xsk_skb_metadata(), prevent TOCTOU by reading csum_start and csum_offset from the userspace-mapped UMEM shared metadata into local variables once, then use the same validated local copies for both checksum bounds validation and for skb assignment in the transmit path.

    Linux kernel (xsk_skb_metadata) csum_start/csum_offset caching in local variables = Read csum_start and csum_offset once into local copies and use those local copies for both bounds validation and subsequent assignment/use (do not re-read from shared UMEM for validation vs assignment).

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-53250?

CVE-2026-53250 has a risk score of 47, indicating a moderate level of severity.

2

How do I fix CVE-2026-53250?

To fix CVE-2026-53250, ensure that your Linux kernel is updated to the latest version that includes the patch for this vulnerability.

3

What systems are affected by CVE-2026-53250?

CVE-2026-53250 affects the Linux kernel and potentially any system running an affected version.

4

What type of vulnerability is CVE-2026-53250?

CVE-2026-53250 is a Time of Check to Time of Use (TOCTOU) vulnerability impacting memory-mapped UMEM buffers in the Linux kernel.

5

When was CVE-2026-53250 published?

CVE-2026-53250 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