GHSA-4G6C-C5FR-62MX

Vulnerability from github – Published: 2026-01-23 15:31 – Updated: 2026-01-23 15:31
VLAI?
Details

In the Linux kernel, the following vulnerability has been resolved:

io_uring/poll: correctly handle io_poll_add() return value on update

When the core of io_uring was updated to handle completions consistently and with fixed return codes, the POLL_REMOVE opcode with updates got slightly broken. If a POLL_ADD is pending and then POLL_REMOVE is used to update the events of that request, if that update causes the POLL_ADD to now trigger, then that completion is lost and a CQE is never posted.

Additionally, ensure that if an update does cause an existing POLL_ADD to complete, that the completion value isn't always overwritten with -ECANCELED. For that case, whatever io_poll_add() set the value to should just be retained.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2025-71149"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-01-23T15:16:05Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/poll: correctly handle io_poll_add() return value on update\n\nWhen the core of io_uring was updated to handle completions\nconsistently and with fixed return codes, the POLL_REMOVE opcode\nwith updates got slightly broken. If a POLL_ADD is pending and\nthen POLL_REMOVE is used to update the events of that request, if that\nupdate causes the POLL_ADD to now trigger, then that completion is lost\nand a CQE is never posted.\n\nAdditionally, ensure that if an update does cause an existing POLL_ADD\nto complete, that the completion value isn\u0027t always overwritten with\n-ECANCELED. For that case, whatever io_poll_add() set the value to\nshould just be retained.",
  "id": "GHSA-4g6c-c5fr-62mx",
  "modified": "2026-01-23T15:31:35Z",
  "published": "2026-01-23T15:31:35Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-71149"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/0126560370ed5217958b85657b590ad25e8b9c00"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/13a8f7b88c2d40c6b33f6216190478dda95d385f"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/84230ad2d2afbf0c44c32967e525c0ad92e26b4e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8b777ab48441b153502772ecfc78c107d4353f29"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c1669c03bfbc2a9b5ebff4428eecebe734c646fe"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


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 observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.