CVE-2026-43442

io_uring: fix physical SQE bounds check for SQE_MIXED 128-byte ops

High · published May 8, 2026

CVSS v3.1
7.1
EPSS
0%
Percentile
6.5
In the wild
Unconfirmed
What it is

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

io_uring: fix physical SQE bounds check for SQE_MIXED 128-byte ops

When IORING_SETUP_SQE_MIXED is used without IORING_SETUP_NO_SQARRAY,

the boundary check for 128-byte SQE operations in io_init_req()

validated the logical SQ head position rather than the physical SQE

index.

The existing check:

!(ctx->cached_sq_head & (ctx->sq_entries - 1))

ensures the logical position isn't at the end of the ring, which is

correct for NO_SQARRAY rings where physical == logical. However, when

sq_array is present, an unprivileged user can remap any logical

position to an arbitrary physical index via sq_array. Setting

sq_array[N] = sq_entries - 1 places a 128-byte operation at the last

physical SQE slot, causing the 128-byte memcpy in

io_uring_cmd_sqe_copy() to read 64 bytes past the end of the SQE

array.

Replace the cached_sq_head alignment check with a direct validation

of the physical SQE index, which correctly handles both sq_array and

NO_SQARRAY cases.

The record
Technical detail
CVSS v3.1
7.1 · HIGH
Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
CVSS v4.0
Not supplied
EPSS
0.00173 · 6.5th percentile
Published
2026-05-08T14:22Z
EPSS history
Timeline
  • 08 MAY 14:22Z
    io_uring: fix physical SQE bounds check for SQE_MIXED 128-byte ops
    cvelistv5