fkie_cve-2025-23138
Vulnerability from fkie_nvd
Published
2025-04-16 15:16
Modified
2025-04-17 20:22
Severity ?
Summary
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()?)
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/205028ebba838938d3b264dda1d0708fa7fe1ade
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/2d680b988656bb556c863d8b46d9b9096842bf3d
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/471c89b7d4f58bd6082f7c1fe14d4ca15c7f1284
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/56ec918e6c86c1536870e4373e91eddd0c44245f
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/6dafa27764183738dc5368b669b71e3d0d154f12
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/8658c75343ed00e5e154ebbe24335f51ba8db547
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/d40e3537265dea9e3c33021874437ff26dc18787
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/f13abc1e8e1a3b7455511c4e122750127f6bc9b0
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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-\u003epipe_bufs without updating the pipe-\u003enr_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-\u003epipe_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\u0027s unclear why watch_queue_set_size() does not update nr_accounted;\nit may be due to intentional overprovisioning in watch_queue_set_size()?)"
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: watch_queue: correcci\u00f3n de la discrepancia en la contabilidad de la tuber\u00eda. Actualmente, watch_queue_set_size() modifica los b\u00faferes de la tuber\u00eda cargados a user-\u0026gt;pipe_bufs sin actualizar pipe-\u0026gt;nr_accounted en la propia tuber\u00eda, debido a la prueba if (!pipe_has_watch_queue()) en pipe_resize_ring(). Esto significa que, cuando la tuber\u00eda se libera finalmente, se decrementa user-\u0026gt;pipe_bufs en un valor distinto al que se le hab\u00eda cargado, lo que podr\u00eda provocar un desbordamiento. Esto, a su vez, puede provocar que las pruebas too_many_pipe_buffers_soft() posteriores fallen con -EPERM. Para remediar esto, tenga en cuenta expl\u00edcitamente el uso de la tuber\u00eda en watch_queue_set_size() para que coincida con el n\u00famero establecido mediante account_pipe_buffers() (no est\u00e1 claro por qu\u00e9 watch_queue_set_size() no actualiza nr_accounted; puede deberse a un exceso de aprovisionamiento intencional en watch_queue_set_size())."
    }
  ],
  "id": "CVE-2025-23138",
  "lastModified": "2025-04-17T20:22:16.240",
  "metrics": {},
  "published": "2025-04-16T15:16:08.163",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/205028ebba838938d3b264dda1d0708fa7fe1ade"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/2d680b988656bb556c863d8b46d9b9096842bf3d"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/471c89b7d4f58bd6082f7c1fe14d4ca15c7f1284"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/56ec918e6c86c1536870e4373e91eddd0c44245f"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/6dafa27764183738dc5368b669b71e3d0d154f12"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/8658c75343ed00e5e154ebbe24335f51ba8db547"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/d40e3537265dea9e3c33021874437ff26dc18787"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/f13abc1e8e1a3b7455511c4e122750127f6bc9b0"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Awaiting Analysis"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.