{"uuid": "457dd838-c615-4ee9-ab72-fa0af897e863", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-23138", "type": "seen", "source": "https://t.me/cvedetector/23111", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-23138 - Linux Kernel Pipe Buffer Underflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-23138 \nPublished : April 16, 2025, 3:16 p.m. | 23\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nwatch_queue: fix pipe accounting mismatch  \n  \nCurrently, watch_queue_set_size() modifies the pipe buffers charged to  \nuser->pipe_bufs without updating the pipe->nr_accounted on the pipe  \nitself, due to the if (!pipe_has_watch_queue()) test in  \npipe_resize_ring(). This means that when the pipe is ultimately freed,  \nwe decrement user->pipe_bufs by something other than what than we had  \ncharged to it, potentially leading to an underflow. This in turn can  \ncause subsequent too_many_pipe_buffers_soft() tests to fail with -EPERM.  \n  \nTo remedy this, explicitly account for the pipe usage in  \nwatch_queue_set_size() to match the number set via account_pipe_buffers()  \n  \n(It's unclear why watch_queue_set_size() does not update nr_accounted;  \nit may be due to intentional overprovisioning in watch_queue_set_size()?) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"16 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T17:43:31.000000Z"}