Answer in brief
CVE-2025-40046 records a Unknown severity vulnerability in io_uring/zcrx: fix overshooting recv limit. 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 | >=6699ec9a23f85f1764183430209c741847c45f12 <8bcc9eaf1b19f1a7029cba19f6bd4122b40f6c4f || >=6699ec9a23f85f1764183430209c741847c45f12 <09cfd3c52ea76f43b3cb15e570aeddf633d65e80 | 8bcc9eaf1b19f1a7029cba19f6bd4122b40f6c4f, 09cfd3c52ea76f43b3cb15e570aeddf633d65e80 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Oct 28, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: io_uring/zcrx: fix overshooting recv limit It's reported that sometimes a zcrx request can receive more than was requested. It's caused by io_zcrx_recv_skb() adjusting desc->count for all received buffers including frag lists, but then doing recursive calls to process frag list skbs, which leads to desc->count double accounting and underflow.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-40046 records a Unknown severity vulnerability in io_uring/zcrx: fix overshooting recv limit. 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 | >=6699ec9a23f85f1764183430209c741847c45f12 <8bcc9eaf1b19f1a7029cba19f6bd4122b40f6c4f || >=6699ec9a23f85f1764183430209c741847c45f12 <09cfd3c52ea76f43b3cb15e570aeddf633d65e80 | 8bcc9eaf1b19f1a7029cba19f6bd4122b40f6c4f, 09cfd3c52ea76f43b3cb15e570aeddf633d65e80 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Oct 28, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: io_uring/zcrx: fix overshooting recv limit It's reported that sometimes a zcrx request can receive more than was requested. It's caused by io_zcrx_recv_skb() adjusting desc->count for all received buffers including frag lists, but then doing recursive calls to process frag list skbs, which leads to desc->count double accounting and underflow.
Quoted source text, attributed separately from HOL analysis.