LiveActive security incident?Get immediate response
CVE Record

CVE-2025-23138: watch_queue: fix pipe accounting mismatch

In the Linux kernel, the following vulnerability has been resolved: watch_queue: fix pipe accounting mismatch Currently, watch_queue_set_size() modifies the pipe buffers charged to user->pipe_bufs without updating the pipe->nr_accounted on the pipe itself, due to the if (!pipe_has_watch_queue()) test in pipe_resize_ring(). This means that when the pipe is ultimately freed, we decrement user->pipe_bufs by something other than what than we had charged to it, potentially leading to an underflow. This in turn can cause subsequent too_many_pipe_buffers_soft() tests to fail with -EPERM. To remedy this, explicitly account for the pipe usage in watch_queue_set_size() to match the number set via account_pipe_buffers() (It's unclear why watch_queue_set_size() does not update nr_accounted; it may be due to intentional overprovisioning in watch_queue_set_size()?)

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

Security readout for executives and security teams

Plain-English summary

CVE-2025-23138 is a Linux kernel bug in watch_queue pipe memory accounting. The described impact is incorrect per-user pipe buffer accounting that can later cause legitimate pipe-buffer checks to fail with EPERM. The sources do not provide a CVSS score, confirmed exploitation, or a broader compromise impact.

Executive priority

Treat as a tracked kernel maintenance issue, not an emergency based on current evidence. Patch through normal expedited Linux update processes, especially for shared infrastructure, while watching vendor advisories for severity or exploitation updates.

Technical view

watch_queue_set_size() charged pipe buffers to user->pipe_bufs without updating pipe->nr_accounted because pipe_resize_ring() skips watch_queue pipes. On pipe free, the kernel can decrement a different amount than it charged, potentially underflowing user->pipe_bufs and disrupting too_many_pipe_buffers_soft() enforcement.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions with watch_queue functionality. The bundle lists Linux as the affected product and includes multiple stable-branch fix references, but distro-specific package status must be checked separately.

Exploitation context

The source bundle does not cite active exploitation, a public exploit, KEV listing, or remote attack conditions. The stated consequence is kernel accounting corruption leading to later EPERM failures, so business impact appears operational unless vendor advisories identify broader effects.

Researcher notes

The useful evidence is the kernel commit rationale: mismatched user->pipe_bufs and pipe->nr_accounted accounting in watch_queue_set_size(). The bundle lacks CVSS, CWE, exploitability analysis, and precise distro package mappings beyond Debian LTS links, so validation should rely on vendor kernel advisories.

Mitigation direction

  • Apply the appropriate Linux kernel stable update or distribution security update.
  • For Debian LTS systems, review the linked Debian LTS announcements for fixed packages.
  • Prioritize externally exposed and multi-user Linux hosts once vendor packages are available.
  • If patch timing is constrained, monitor vendor guidance for any named workaround.

Validation and detection

  • Inventory Linux kernel versions across servers, containers hosts, and appliances.
  • Compare installed kernels against vendor advisories and the listed stable fix references.
  • Check whether Debian LTS packages from the linked announcements are installed where applicable.
  • After updating, confirm systems boot the fixed kernel, not only install it.
Prepared
Confidence
medium
Sources
12

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-2025-23138 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
1ADP providers
11Source 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.

ADP provider summaries

CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux162ae0e78bdabf84ef10c1293c4ed7865cb7d3c8, 3efbd114b91525bb095b8ae046382197d92126b9, b87a1229d8668fbc78ebd9ca0fc797a76001c60f, 68e51bdb1194f11d3452525b99c98aff6f837b24, e95aada4cb93d42e25c30a0ef9eb2923d9711d4a, e95aada4cb93d42e25c30a0ef9eb2923d9711d4a, e95aada4cb93d42e25c30a0ef9eb2923d9711d4a, e95aada4cb93d42e25c30a0ef9eb2923d9711d4a, 6fb70694f8d1ac34e45246b0ac988f025e1e5b55, 5.10.210, 5.15.149, 6.1.76, 6.6.15, 6.7.3unaffected
LinuxLinux6.8, 0, 5.10.236, 5.15.180, 6.1.134, 6.6.87, 6.12.23, 6.13.11, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

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