CVE-2026-53250

xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata()

State
Published
Severity
7.8 High
Published
Jun 25, 2026
Updated
Oct 19, 2026
Reserved
Jun 9, 2026

Read the record on cve.org

Description

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

xsk: cache csum_start/csum_offset to fix TOCTOU in xsk_skb_metadata()

The TX metadata area resides in the UMEM buffer which is memory-mapped and concurrently writable by userspace. In xsk_skb_metadata(), csum_start and csum_offset 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 csum_start and csum_offset into local variables once, then using the local copies for both validation and assignment.

Note that other metadata fields (flags, launch_time) 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.

Scores

CVSSScoreVectorSource
3.17.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

  • CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition

Affected Products

ProductVersions
LinuxLinux
  • 48eb03dd26304c24f03bdbb9382e89c8564e71df to before eb778aed8a9b2381668fcb1247ae4fa011224768Affected
  • 48eb03dd26304c24f03bdbb9382e89c8564e71df to before 0dfe05b938435892875e07771170051346412df9Affected
  • 48eb03dd26304c24f03bdbb9382e89c8564e71df to before bfdfd2706d5fb2cd496a1506e680daf979309c8bAffected
  • 48eb03dd26304c24f03bdbb9382e89c8564e71df to before 22ba97ea9cc1f63a0d0244fae38057ed452b6ac7Affected
LinuxLinux
  • 6.8Affected
  • before 6.8Not affected
  • 6.12.110 through 6.12.*Not affected
  • 6.18.36 through 6.18.*Not affected
  • 7.0.13 through 7.0.*Not affected
  • 7.1 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.