Security Resilience

CVE-2026-23275

Race Condition in Linux Kernel 6.13 – 6.18.19

Published
20 March 2026
Modified
19 October 2026
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.00099 0.8th percentile
Risk Priority 54 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-23275 is a high-severity Race Condition (CWE-362) vulnerability in Linux Kernel. Its CVSS base score is 7.8 (High).

Operationally, ranked at the 0.8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-23275 is a vulnerability in the Linux kernel's io_uring subsystem, where task work flags manipulation on ctx->rings is not stable during ring resizing when DEFER_TASKRUN or SETUP_TASKRUN modes are active. Specifically, if task work is added while the ring is being resized, a race condition can occur in the narrow window between swapping to new rings and freeing the old ones, allowing erroneous OR'ing of the IORING_SQ_TASKRUN flag. This affects Linux kernel versions supporting io_uring with ring resizing in DEFER_TASKRUN mode.

A local attacker with low privileges (PR:L) can exploit this vulnerability with low attack complexity and no user interaction required, as indicated by its CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Successful exploitation could result in high impacts to confidentiality, integrity, and availability, potentially enabling privilege escalation, data corruption, or system crashes through the race condition in io_uring operations.

The provided patch references detail the mitigation via kernel commits that introduce a secondary ->rings_rcu pointer protected by RCU to ensure stability during task work flag operations. Ring freeing after resize is performed post-RCU synchronize(), avoiding locks in the fast path of task work additions. This fix applies specifically to DEFER_TASKRUN mode, the only one supporting resizing, and uses the io_ctx_mark_taskrun() helper; other modes would require similar handling if extended.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

In the Linux kernel, the following vulnerability has been resolved: io_uring: ensure ctx->rings is stable for task work flags manipulation If DEFER_TASKRUN | SETUP_TASKRUN is used and task work is added while the ring is being resized, it's possible for…

more

the OR'ing of IORING_SQ_TASKRUN to happen in the small window of swapping into the new rings and the old rings being freed. Prevent this by adding a 2nd ->rings pointer, ->rings_rcu, which is protected by RCU. The task work flags manipulation is inside RCU already, and if the resize ring freeing is done post an RCU synchronize, then there's no need to add locking to the fast path of task work additions. Note: this is only done for DEFER_TASKRUN, as that's the only setup mode that supports ring resizing. If this ever changes, then they too need to use the io_ctx_mark_taskrun() helper.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-57974Same product: Linux Linux Kernel
CVE-2026-31676Same product: Linux Linux Kernel
CVE-2026-23071Same product: Linux Linux Kernel
CVE-2026-45942Same product: Linux Linux Kernel
CVE-2024-44954Same product: Linux Linux Kernel
CVE-2024-38628Same product: Linux Linux Kernel
CVE-2026-46137Same product: Linux Linux Kernel
CVE-2023-53094Same product: Linux Linux Kernel
CVE-2025-71183Same product: Linux Linux Kernel
CVE-2024-53136Same product: Linux Linux Kernel

Affected Assets

linux
linux kernel
7.0 · 6.13 — 6.18.19 · 6.19 — 6.19.9

Mitigating Controls

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-362

Accurate timestamps from internal clocks enable detection of race conditions by providing reliable event ordering in audit logs.

addresses: CWE-362

Coordination of concurrent security activities reduces the probability that shared resources will be accessed simultaneously without proper synchronization.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect race conditions, but does not prevent them at design or coding time.

prevents

Secure coding standards explicitly forbid unsafe concurrent access patterns and mandate atomic operations or locks.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-362, a class-level weakness, and none of its children carries one either.

References