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

ublk: use READ_ONCE() to read struct ublksrv_ctrl_cmd

struct ublksrv_ctrl_cmd is part of the io_uring_sqe, which may lie in
userspace-mapped memory. It's racy to access its fields with normal
loads, as userspace may write to them concurrently. Use READ_ONCE() to
copy the ublksrv_ctrl_cmd from the io_uring_sqe to the stack. Use the
local copy in place of the one in the io_uring_sqe.
Published: 2026-05-27
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A data race exists in the Linux kernel’s ublk subsystem where the ublksrv_ctrl_cmd structure located in a userspace‑mapped io_uring submission queue entry is accessed with normal loads. Because the kernel may read this structure concurrently while userspace writes to it, the loaded values can be torn or stale, potentially causing the kernel to interpret an incorrect command. This flaw could allow an attacker to influence the device command processing and potentially execute an unintended operation or destabilize the kernel. The underlying weakness is a race condition that violates proper atomic access to shared data.

Affected Systems

All Linux kernel implementations that expose the ublk driver and allow userspace applications to submit io_uring submission queue entries containing ublksrv_ctrl_cmd structures are affected. The bug exists in every kernel release until the patch that introduces the READ_ONCE() macro to copy the structure to the stack is applied.

Risk and Exploitability

The CVSS score is not provided and the EPSS score is unavailable, suggesting no known widespread exploitation. The flaw is listed as not present in the CISA KEV catalog, indicating it has not yet been featured in publicly known exploits. Nonetheless, the race condition can be triggered when an attacker can write to the userspace memory mapped into the kernel, so any user space program that interacts with ublk through io_uring may be a potential attack vector. The threat level is therefore considered moderate, but the recommended action is to patch the kernel before any attackers can take advantage.

Generated by OpenCVE AI on May 27, 2026 at 17:14 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes the ublk READ_ONCE fix
  • If a kernel upgrade is not possible, disable the ublk driver or avoid using io_uring submission queue entries that map userspace memory containing ublksrv_ctrl_cmd structures
  • Monitor official Linux kernel advisories and security mailing lists for further updates or workarounds

Generated by OpenCVE AI on May 27, 2026 at 17:14 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 27 May 2026 17:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-362
CWE-564

Wed, 27 May 2026 14:15:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ublk: use READ_ONCE() to read struct ublksrv_ctrl_cmd struct ublksrv_ctrl_cmd is part of the io_uring_sqe, which may lie in userspace-mapped memory. It's racy to access its fields with normal loads, as userspace may write to them concurrently. Use READ_ONCE() to copy the ublksrv_ctrl_cmd from the io_uring_sqe to the stack. Use the local copy in place of the one in the io_uring_sqe.
Title ublk: use READ_ONCE() to read struct ublksrv_ctrl_cmd
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-05-27T12:18:33.939Z

Reserved: 2026-05-13T15:03:33.090Z

Link: CVE-2026-45975

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-05-27T14:17:14.590

Modified: 2026-05-27T14:48:03.013

Link: CVE-2026-45975

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-05-27T21:30:34Z

Weaknesses