Answer in brief
CVE-2025-23138 records a Medium severity (CVSS 5.5) vulnerability in watch_queue: fix pipe accounting mismatch. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=162ae0e78bdabf84ef10c1293c4ed7865cb7d3c8 <8658c75343ed00e5e154ebbe24335f51ba8db547 || >=3efbd114b91525bb095b8ae046382197d92126b9 <471c89b7d4f58bd6082f7c1fe14d4ca15c7f1284 || >=b87a1229d8668fbc78ebd9ca0fc797a76001c60f <d40e3537265dea9e3c33021874437ff26dc18787 || >=68e51bdb1194f11d3452525b99c98aff6f837b24 <6dafa27764183738dc5368b669b71e3d0d154f12 || >=e95aada4cb93d42e25c30a0ef9eb2923d9711d4a <56ec918e6c86c1536870e4373e91eddd0c44245f || >=e95aada4cb93d42e25c30a0ef9eb2923d9711d4a <2d680b988656bb556c863d8b46d9b9096842bf3d || >=e95aada4cb93d42e25c30a0ef9eb2923d9711d4a <205028ebba838938d3b264dda1d0708fa7fe1ade || >=e95aada4cb93d42e25c30a0ef9eb2923d9711d4a <f13abc1e8e1a3b7455511c4e122750127f6bc9b0 || 6fb70694f8d1ac34e45246b0ac988f025e1e5b55 || >=5.10.210 <5.10.236 || >=5.15.149 <5.15.180 || >=6.1.76 <6.1.134 || >=6.6.15 <6.6.87 || >=6.7.3 <6.8 | 8658c75343ed00e5e154ebbe24335f51ba8db547, 471c89b7d4f58bd6082f7c1fe14d4ca15c7f1284, d40e3537265dea9e3c33021874437ff26dc18787, 6dafa27764183738dc5368b669b71e3d0d154f12, 56ec918e6c86c1536870e4373e91eddd0c44245f, 2d680b988656bb556c863d8b46d9b9096842bf3d, 205028ebba838938d3b264dda1d0708fa7fe1ade, f13abc1e8e1a3b7455511c4e122750127f6bc9b0, 5.10.236, 5.15.180, 6.1.134, 6.6.87, 6.8 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Apr 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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()?)
Quoted source text, attributed separately from HOL analysis.