Answer in brief
CVE-2026-97618 records a Unknown severity vulnerability in io_uring/net: don't overconsume buffers when using MSG_TRUNC. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ae98dbf43d755b4e111fcd086e53939bef3e9a1a <927d96f91c582b319d104ecf50ec935a8dc29193 || >=ae98dbf43d755b4e111fcd086e53939bef3e9a1a <2e70ea75c7bb38a6dc212975f887310f14f7c043 || >=ae98dbf43d755b4e111fcd086e53939bef3e9a1a <6028b543884f8735e057ec9eea4908cd61cab230 | 927d96f91c582b319d104ecf50ec935a8dc29193, 2e70ea75c7bb38a6dc212975f887310f14f7c043, 6028b543884f8735e057ec9eea4908cd61cab230 |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
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]
Quoted source text, attributed separately from HOL analysis.