Answer in brief
CVE-2025-40292 records a High severity (CVSS 8.4) vulnerability in virtio-net: fix received length check in big packets. 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.
CVSS is 8.4. 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 | >=4959aebba8c06992abafa09d1e80965e0825af54 <82f9028e83944a9eee5229cbc6fee9be1de8a62d || >=4959aebba8c06992abafa09d1e80965e0825af54 <946dec89c41726b94d31147ec528b96af0be1b5a || >=4959aebba8c06992abafa09d1e80965e0825af54 <82fe78065450d2d07f36a22e2b6b44955cf5ca5b || >=4959aebba8c06992abafa09d1e80965e0825af54 <3e9d89f2ecd3636bd4cbdfd0b2dfdaf58f9882e2 || >=4959aebba8c06992abafa09d1e80965e0825af54 <0c716703965ffc5ef4311b65cb5d84a703784717 | 82f9028e83944a9eee5229cbc6fee9be1de8a62d, 946dec89c41726b94d31147ec528b96af0be1b5a, 82fe78065450d2d07f36a22e2b6b44955cf5ca5b, 3e9d89f2ecd3636bd4cbdfd0b2dfdaf58f9882e2, 0c716703965ffc5ef4311b65cb5d84a703784717 |
| Linux/Linuxgeneric | 6.1 | Not reported |
Published upstream
Dec 8, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
In the Linux kernel, the following vulnerability has been resolved: virtio-net: fix received length check in big packets Since commit 4959aebba8c0 ("virtio-net: use mtu size as buffer length for big packets"), when guest gso is off, the allocated size for big packets is not MAX_SKB_FRAGS * PAGE_SIZE anymore but depends on negotiated MTU. The number of allocated frags for big packets is stored in vi->big_packets_num_skbfrags. Because the host announced buffer length can be malicious (e.g. the host vhost_net driver's get_rx_bufs is modified to announce incorrect length), we need a check in virtio_net receive path. Currently, the check is not adapted to the new change which can lead to NULL page pointer dereference in the below while loop when receiving length that is larger than the allocated one. This commit fixes the received length check corresponding to the new change.
Quoted source text, attributed separately from HOL analysis.