LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23263: io_uring/zcrx: fix page array leak

In the Linux kernel, the following vulnerability has been resolved: io_uring/zcrx: fix page array leak d9f595b9a65e ("io_uring/zcrx: fix leaking pages on sg init fail") fixed a page leakage but didn't free the page array, release it as well.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a memory/resource leak in the io_uring zero-copy receive path. The public record describes a missed free of a page array after an initialization failure. No CVSS score, CWE, or active exploitation evidence is provided, so urgency depends on whether affected kernel versions are deployed.

Executive priority

Track and patch through normal kernel maintenance unless vendor guidance raises severity. Escalate for multi-tenant or high-availability systems if affected kernels are confirmed.

Technical view

CVE-2026-23263 resolves a leak in io_uring/zcrx. A prior fix released leaked pages on scatter-gather initialization failure but did not release the page array itself. The supplied record lists Linux kernel versions as affected and points to stable kernel commits as fixes, but gives no exploitability details.

Likely exposure

Exposure is likely limited to Linux systems running kernel versions identified as affected in the CVE record, particularly where io_uring zero-copy receive code is present. The source bundle does not identify distributions, configurations, containers, or cloud images affected.

Exploitation context

The provided sources do not report active exploitation, and KEV is false. The available evidence supports a kernel resource leak, not a confirmed remote compromise path. Required privileges, trigger conditions, and practical impact are not stated.

Researcher notes

Evidence is sparse: the CVE text identifies a missed free of a page array in io_uring/zcrx and two stable commit references. There is no CVSS, CWE, proof of exploitation, affected distribution list, or stated attack prerequisite in the supplied bundle.

Mitigation direction

  • Review vendor kernel advisories for CVE-2026-23263 applicability.
  • Update to kernel builds containing the referenced stable fixes.
  • Prioritize internet-facing and multi-tenant Linux systems after vendor confirmation.
  • Monitor kernel vendor channels for severity, CVSS, and backport details.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and images.
  • Compare deployed kernels against vendor advisories for this CVE.
  • Check whether updates include the referenced stable kernel commits.
  • Record systems awaiting vendor fixes or maintenance windows.
Prepared
Confidence
medium
Sources
4

Public sources used

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-23263 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb84621d96ee0221e0bfbf9f477bbec7a5077c464, b84621d96ee0221e0bfbf9f477bbec7a5077c464unaffected
LinuxLinux6.17, 0, 6.18.10, 6.19affected
Weakness

CWE details

No CWE listed

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