In the Linux kernel, the following vulnerability has been resolved: io_uring/net: don't...

zetlyn/cve-ghsa vulnerability ghsa GHSA-qrrw-9q98-7ph9 cve CVE-2026-97618 known 2026-09-25

https://github.com/advisories/GHSA-qrrw-9q98-7ph9

Properties

severityunknown
receipt
Source
GitHub advisories
Its words
unknown
Read by
field:severity
Said since
2026-09-28 11:44 UTC
Last answered
2026-10-06 13:46 UTC
Original
open at the source
What the source handed over
{
  "credits": [],
  "cve_id": "CVE-2026-97618",
  "cvss": {
    "score": null,
    "vector_string": null
  },
  "cvss_severities": {
    "cvss_v3": {
      "score": 0.0,
      "vector_string": null
    },
    "cvss_v4": {
      "score": 0.0,
      "vector_string": null
    }
  },
  "cwes": [],
  "description": "In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: don't overconsume buffers when using MSG_TRUNC\n\nWhen a recv/recvmsg is issued with MSG_TRUNC and the incoming packet is\nlarger than the provided buffer, the net layer returns the full length\nof the packet rather than the number of bytes actually copied into the\nbuffer.  As a result, io_uring advances more of the provided buffer ring\nthan was actually filled.  Use the actual filled region size to consume\nthe buffer, but still return the full size to preserve MSG_TRUNC\nsemantics.\n\nTake care with multishot, because that seems to already truncate the\nconsumption based on the available payload size.\n\nThis was reported in https://github.com/axboe/liburing/issues/1619.\n\n[axboe: fold in size_t unsigned fix]",
  "epss": {
    "percentage": 0.00198,
    "percentile": 0.08618
  },
  "ghsa_id": "GHSA-qrrw-9q98-7ph9",
  "github_reviewed_at": null,
  "html_url": "https://github.com/advisories/GHSA-qrrw-9q98-7ph9",
  "identifiers": [
    {
      "type": "GHSA",
      "value": "GHSA-qrrw-9q98-7ph9"
    },
    {
      "type": "CVE",
      "value": "CVE-2026-97618"
    }
  ],
  "nvd_published_at": "2026-09-25T11:17:16Z",
  "published_at": "2026-09-25T12:31:27Z",
  "references": [
    "https://nvd.nist.gov/vuln/detail/CVE-2026-97618",
    "https://git.kernel.org/stable/c/2e70ea75c7bb38a6dc212975f887310f14f7c043",
    "https://git.kernel.org/stable/c/6028b543884f8735e057ec9eea4908cd61cab230",
    "https://git.kernel.org/stable/c/927d96f91c582b319d104ecf50ec935a8dc29193",
    "https://github.com/advisories/GHSA-qrrw-9q98-7ph9"
  ],
  "repository_advisory_url": null,
  "severity": "unknown",
  "source_code_location": "",
  "summary": "In the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: don't...",
  "type": "unreviewed",
  "updated_at": "2026-09-25T12:31:33Z",
  "url": "https://api.github.com/advisories/GHSA-qrrw-9q98-7ph9",
  "vulnerabilities": [],
  "withdrawn_at": null
}

Text

In the Linux kernel, the following vulnerability has been resolved: io_uring/net: don't... In the Linux kernel, the following vulnerability has been resolved: io_uring/net: don't overconsume buffers when using MSG_TRUNC When a recv/recvmsg is issued with MSG_TRUNC and the incoming packet is larger than the provided buffer, the net layer returns the full length of the packet rather than the number of bytes actually copied into the buffer. As a result, io_uring advances more of the provided buffer ring than was actually filled. Use the actual filled region size to consume the buffer, but still return the full size to preserve MSG_TRUNC semantics. Take care with multishot, because that seems to already truncate the consumption based on the available payload size. This was reported in https://github.com/axboe/liburing/issues/1619. [axboe: fold in size_t unsigned fix]