CVE-2025-40292

virtio-net: fix received length check in big packets

HIGH
8.4
CVSS Score
Published: December 8, 2025 at 12:46 AM UTC
Updated: October 15, 2026 at 10:19 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.4
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4959aebba8c06992abafa09d1e80965e0825af546.1
Vendor states this is fixed in 0c716703965ffc5ef4311b65cb5d84a703784717 (fixed)
Vendor states this is fixed in 3e9d89f2ecd3636bd4cbdfd0b2dfdaf58f9882e2 (fixed)
Vendor states this is fixed in 82f9028e83944a9eee5229cbc6fee9be1de8a62d (fixed)
Vendor states this is fixed in 82fe78065450d2d07f36a22e2b6b44955cf5ca5b (fixed)
Vendor states this is fixed in 946dec89c41726b94d31147ec528b96af0be1b5a (fixed)
Vendor states this is fixed in 6.1 (unaffected)
Vendor states this is fixed in 6.1.159 (unaffected)
Vendor states this is fixed in 6.12.58 (unaffected)
Vendor states this is fixed in 6.17.8 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.6.117 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.4HIGHLinux
Vector?

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card