CVE-2025-40292

virtio-net: fix received length check in big packets

State
Published
Severity
8.4 High
Published
Dec 8, 2025
Updated
Oct 15, 2026
Reserved
Apr 16, 2025

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.18.4 HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 4959aebba8c06992abafa09d1e80965e0825af54 to before 82f9028e83944a9eee5229cbc6fee9be1de8a62dAffected
  • 4959aebba8c06992abafa09d1e80965e0825af54 to before 946dec89c41726b94d31147ec528b96af0be1b5aAffected
  • 4959aebba8c06992abafa09d1e80965e0825af54 to before 82fe78065450d2d07f36a22e2b6b44955cf5ca5bAffected
  • 4959aebba8c06992abafa09d1e80965e0825af54 to before 3e9d89f2ecd3636bd4cbdfd0b2dfdaf58f9882e2Affected
  • 4959aebba8c06992abafa09d1e80965e0825af54 to before 0c716703965ffc5ef4311b65cb5d84a703784717Affected
LinuxLinux
  • 6.1Affected
  • before 6.1Not affected
  • 6.1.159 through 6.1.*Not affected
  • 6.6.117 through 6.6.*Not affected
  • 6.12.58 through 6.12.*Not affected
  • 6.17.8 through 6.17.*Not affected
  • 6.18 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.