LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52926: io_uring/rw: split io_read() into a helper

In the Linux kernel, the following vulnerability has been resolved: IORING_OP_READ did not correctly consume the provided buffer list when read i/o returned < 0 (except for -EAGAIN and -EIOCBQUEUED return). This can lead to a potential use-after-free when the completion via io_rw_done runs at separate context.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory-safety flaw in io_uring read handling. A local user or workload could potentially trigger a use-after-free, risking privilege impact on the affected host. It is not remotely exploitable based on the CVSS vector provided.

Executive priority

Treat this as a high-priority kernel patching issue for shared Linux infrastructure. It is less urgent than an internet-facing remote exploit, but local privilege-impact kernel bugs can materially worsen breaches once attackers obtain footholds.

Technical view

IORING_OP_READ mishandled provided buffer-list consumption when read I/O returned some negative errors, excluding -EAGAIN and -EIOCBQUEUED. Completion in a separate context could then lead to use-after-free. The CVE maps this to CWE-416 with CVSS 7.8, local, low-complexity, low-privilege impact.

Likely exposure

Systems running affected Linux kernel versions are in scope, especially multi-user hosts, container platforms, developer machines, and shared workloads where local code execution is possible. Exact exposure depends on distribution kernel backports and whether the referenced stable fixes are present.

Exploitation context

The provided bundle does not show active exploitation, and KEV is false. The risk is local post-access escalation or host compromise, not initial remote entry. Public sources provided identify kernel fixes and a Debian LTS advisory, but no exploit status.

Researcher notes

Focus validation on io_uring-capable kernels and downstream backports. The core condition is incorrect provided-buffer handling on certain negative read returns, followed by completion in another context. Sources do not provide a proof of concept or exploitation telemetry.

Mitigation direction

  • Update affected Linux kernels through the relevant vendor or distribution channel.
  • Confirm the update includes the referenced upstream stable fixes.
  • Prioritize shared systems where untrusted local users or workloads can run code.
  • Follow Debian LTS guidance where Debian kernels are deployed.
  • If patching is delayed, check vendor guidance for supported compensating controls.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, and container hosts.
  • Map each kernel to distribution advisories and backported fix status.
  • Verify whether the referenced stable commits are included in deployed kernels.
  • Run authenticated vulnerability checks after kernel updates and reboot.
  • Document exceptions where vendor fix status is unclear.
Prepared
Confidence
high
Sources
6

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.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-52926 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
0Timeline events
0ADP providers
5Source 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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2023-52926Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2b188cc1bb857a9d4701ae59aa7768b5124e262e, 2b188cc1bb857a9d4701ae59aa7768b5124e262e, 2b188cc1bb857a9d4701ae59aa7768b5124e262eunaffected
LinuxLinux5.1, 0, 6.1.122, 6.6.68, 6.7affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.