GHSA-W3XC-H2CH-2Q3Q

Vulnerability from github – Published: 2026-05-01 15:30 – Updated: 2026-05-03 09:33
VLAI?
Details

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

io_uring/net: fix slab-out-of-bounds read in io_bundle_nbufs()

sqe->len is __u32 but gets stored into sr->len which is int. When userspace passes sqe->len values exceeding INT_MAX (e.g. 0xFFFFFFFF), sr->len overflows to a negative value. This negative value propagates through the bundle recv/send path:

  1. io_recv(): sel.val = sr->len (ssize_t gets -1)
  2. io_recv_buf_select(): arg.max_len = sel->val (size_t gets 0xFFFFFFFFFFFFFFFF)
  3. io_ring_buffers_peek(): buf->len is not clamped because max_len is astronomically large
  4. iov[].iov_len = 0xFFFFFFFF flows into io_bundle_nbufs()
  5. io_bundle_nbufs(): min_t(int, 0xFFFFFFFF, ret) yields -1, causing ret to increase instead of decrease, creating an infinite loop that reads past the allocated iov[] array

This results in a slab-out-of-bounds read in io_bundle_nbufs() from the kmalloc-64 slab, as nbufs increments past the allocated iovec entries.

BUG: KASAN: slab-out-of-bounds in io_bundle_nbufs+0x128/0x160 Read of size 8 at addr ffff888100ae05c8 by task exp/145 Call Trace: io_bundle_nbufs+0x128/0x160 io_recv_finish+0x117/0xe20 io_recv+0x2db/0x1160

Fix this by rejecting negative sr->len values early in both io_sendmsg_prep() and io_recvmsg_prep(). Since sqe->len is __u32, any value > INT_MAX indicates overflow and is not a valid length.

Severity ?
7.1 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-31774"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-125"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-01T15:16:40Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: fix slab-out-of-bounds read in io_bundle_nbufs()\n\nsqe-\u003elen is __u32 but gets stored into sr-\u003elen which is int. When\nuserspace passes sqe-\u003elen values exceeding INT_MAX (e.g. 0xFFFFFFFF),\nsr-\u003elen overflows to a negative value. This negative value propagates\nthrough the bundle recv/send path:\n\n  1. io_recv(): sel.val = sr-\u003elen (ssize_t gets -1)\n  2. io_recv_buf_select(): arg.max_len = sel-\u003eval (size_t gets\n     0xFFFFFFFFFFFFFFFF)\n  3. io_ring_buffers_peek(): buf-\u003elen is not clamped because max_len\n     is astronomically large\n  4. iov[].iov_len = 0xFFFFFFFF flows into io_bundle_nbufs()\n  5. io_bundle_nbufs(): min_t(int, 0xFFFFFFFF, ret) yields -1,\n     causing ret to increase instead of decrease, creating an\n     infinite loop that reads past the allocated iov[] array\n\nThis results in a slab-out-of-bounds read in io_bundle_nbufs() from\nthe kmalloc-64 slab, as nbufs increments past the allocated iovec\nentries.\n\n  BUG: KASAN: slab-out-of-bounds in io_bundle_nbufs+0x128/0x160\n  Read of size 8 at addr ffff888100ae05c8 by task exp/145\n  Call Trace:\n   io_bundle_nbufs+0x128/0x160\n   io_recv_finish+0x117/0xe20\n   io_recv+0x2db/0x1160\n\nFix this by rejecting negative sr-\u003elen values early in both\nio_sendmsg_prep() and io_recvmsg_prep(). Since sqe-\u003elen is __u32,\nany value \u003e INT_MAX indicates overflow and is not a valid length.",
  "id": "GHSA-w3xc-h2ch-2q3q",
  "modified": "2026-05-03T09:33:10Z",
  "published": "2026-05-01T15:30:35Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-31774"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/1b655cd311344117d3052f6552cb20d9901c9d7c"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/90ced24c500ad4e129e9e34b7e56fd7849e350b6"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b948f9d5d3057b01188e36664e7c7604d1c8ecb5"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c314b405dcc4d8b9041124f928f81715d6328bec"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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.