LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38504: io_uring/zcrx: fix pp destruction warnings

In the Linux kernel, the following vulnerability has been resolved: io_uring/zcrx: fix pp destruction warnings With multiple page pools and in some other cases we can have allocated niovs on page pool destruction. Remove a misplaced warning checking that all niovs are returned to zcrx on io_pp_zc_destroy(). It was reported before but apparently got lost.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel CVE describes a bug in io_uring zero-copy receive cleanup that could trigger incorrect page-pool destruction warnings. The source bundle does not describe data theft, code execution, denial of service, or a clear business impact. Treat it as a kernel maintenance/security update until vendor guidance says more.

Executive priority

Medium operational priority, not emergency priority, based on current evidence. Patch through normal kernel update processes, but escalate if your Linux vendor assigns severity, impact, or exploitation details not present here.

Technical view

The issue is in Linux io_uring/zcrx page-pool cleanup. The fix removes a misplaced warning in io_pp_zc_destroy() because allocated niovs can still exist during page-pool destruction in multi-page-pool and other cases. No CWE, CVSS, exploit primitive, or impact class is provided.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds around 6.15 before the stable fixes referenced by kernel.org. The bundle also lists affected git commit 34a3e60821ab9f335a58d43a88cccdbefdebdec3. Exact product distribution exposure is not provided.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not marked KEV. No public exploit behavior, attack path, required privileges, or remote/local context is described in the bundle.

Researcher notes

The record is sparse: no CVSS, CWE, impact statement, exploitability details, or distribution-specific status. Analysis should stay close to the kernel commit language and avoid assuming memory corruption, privilege escalation, or denial of service without further evidence.

Mitigation direction

  • Check Linux distribution advisories for CVE-2025-38504 coverage.
  • Plan kernel updates to versions containing the referenced stable fixes.
  • Prioritize internet-facing or untrusted workload hosts if affected.
  • Avoid inventing compensating controls until vendor guidance is available.

Validation and detection

  • Inventory Linux kernel versions across production and staging systems.
  • Compare running kernels with vendor advisories and fixed stable commits.
  • Confirm whether io_uring/zcrx-capable kernels are deployed in sensitive environments.
  • Document any systems awaiting vendor kernel packages.
Prepared
Confidence
medium
Sources
4

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-2025-38504 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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux34a3e60821ab9f335a58d43a88cccdbefdebdec3, 34a3e60821ab9f335a58d43a88cccdbefdebdec3unaffected
LinuxLinux6.15, 0, 6.15.7, 6.16affected
Weakness

CWE details

No CWE listed

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