Skip to main content

Linux Kernel EUVDEUVD-2026-39201

| CVE-2026-53250 HIGH
Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367)
2026-06-25 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-cx83-hxfr-m85v
7.8
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
7.0 HIGH

Local AF_XDP access needs privilege (PR:L) and exploitation hinges on winning a narrow TOCTOU race (AC:H); kernel memory corruption yields full C:H/I:H/A:H.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
7.0 HIGH
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Red Hat
7.0 MEDIUM
qualitative

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Jun 28, 2026 - 09:44 vuln.today
CVSS changed
Jun 28, 2026 - 08:22 NVD
7.8 (HIGH)
Patch available
Jun 25, 2026 - 10:32 EUVD
CVE Published
Jun 25, 2026 - 09:16 cve.org
HIGH 7.8
CVE Published
Jun 25, 2026 - 09:16 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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.

AnalysisAI

Out-of-bounds kernel memory access in the Linux kernel's AF_XDP (xsk) transmit path allows a local low-privileged process to bypass bounds checking on TX checksum metadata. Because csum_start/csum_offset live in a userspace-mapped UMEM buffer, a malicious application could race to overwrite them between the validation read and the assignment read in xsk_skb_metadata(), defeating the bounds check during checksum computation. No public exploit identified at time of analysis; EPSS is low (0.18%, 8th percentile), consistent with a local-only kernel race rather than a mass-exploited remote bug.

Technical ContextAI

The flaw lives in AF_XDP (XDP sockets / xsk), the kernel's high-performance zero-copy packet I/O framework. AF_XDP places TX metadata - including checksum offload fields csum_start and csum_offset - in the UMEM region, which is memory-mapped and remains writable by userspace even while the kernel processes it. xsk_skb_metadata() originally read these fields twice: once to validate them against skb bounds, and again to assign them for hardware/software checksum computation. This is a classic time-of-check-to-time-of-use (TOCTOU, CWE-367) race; because the second read can return attacker-mutated values, it leads to an out-of-bounds write/read (CWE-787/CWE-125) when the checksum routine uses an unvalidated offset. The fix snapshots both fields into local variables once, so validation and use operate on identical values.

RemediationAI

Vendor-released patch: upgrade to a fixed stable kernel - 6.18.36, 7.0.13, or 7.1 (or later) - which snapshots csum_start/csum_offset into local variables before validation. Apply the corresponding stable commits (0dfe05b9, 22ba97ea, bfdfd270) from https://git.kernel.org/ if you maintain your own kernel, or install your distribution's patched kernel package and reboot. If immediate patching is not possible, reduce exposure by restricting who can open AF_XDP sockets: AF_XDP TX typically requires CAP_NET_RAW/CAP_NET_ADMIN, so removing those capabilities from untrusted processes/containers and avoiding granting them in unprivileged user namespaces blocks the attack - the trade-off is that legitimate workloads relying on AF_XDP zero-copy networking will lose that capability. Where AF_XDP is not needed, disabling or not loading the feature for untrusted tenants removes the attack surface entirely.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

EUVD-2026-39201 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy