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.
Security readout for executives and security teams
Plain-English summary
A low-privileged local user can trigger an out-of-bounds kernel read through a specific io_uring configuration. The flaw may expose sensitive kernel memory or crash the system. It is not remotely exploitable according to the supplied CVSS vector, and the bundle provides no evidence of active exploitation.
Executive priority
Prioritize patching multi-user or otherwise untrusted systems where local users can invoke io_uring. Internet exposure alone does not create the stated attack path, but successful local abuse could disclose sensitive memory or interrupt service. Treat exact version determination as an immediate validation task.
Technical view
With SQE_MIXED enabled and NO_SQARRAY absent, an attacker can map a logical queue position to the final physical SQE slot. A 128-byte operation then copies 64 bytes beyond the SQE array because validation used the logical head instead of the physical index. The cited kernel changes validate the physical index directly.
Likely exposure
Exposure requires local, low-privileged access and permission to use the affected io_uring configuration. The bundle identifies Linux 6.19, 6.19.9, and 7.0 as affected, but includes an ambiguous โ0โ entry. Confirm exact affected ranges with the Linux or distribution vendor.
Exploitation context
The supplied CVSS score is 7.1, reflecting possible high confidentiality and availability impact without user interaction. KEV is false, and no cited source establishes active exploitation. The available evidence supports potential memory disclosure or system disruption, not integrity compromise or remote attack.
Researcher notes
The defect is a logical-versus-physical index validation error in io_init_req(). It affects 128-byte SQEs when an SQ array can redirect a valid logical position to the final physical slot. The resulting copy reads 64 bytes out of bounds. The bundle supplies fixes but no exploit evidence, CWE assignment, or fully clear version ranges.
Mitigation direction
Apply a vendor kernel update containing one of the cited physical-index validation fixes.
Confirm distribution advisories because the supplied affected-version data is ambiguous.
Restrict unnecessary local accounts and access to affected systems until patched.
Review existing controls that limit untrusted use of io_uring.
Validation and detection
Record running kernel versions and compare them with vendor advisories for CVE-2026-43442.
Verify the installed kernel includes the cited upstream or stable fix.
Identify systems where unprivileged users can access io_uring.
After updating, reboot where required and confirm the fixed kernel is running.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve ยท low confidence lookup
CVE-2026-43442 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
3Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.