virtio-net: fix received length check in big packets
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0c716703965ffc5ef4311b65cb5d84a703784717, Kernel 3e9d89f2ecd3636bd4cbdfd0b2dfdaf58f9882e2, Kernel 82f9028e83944a9eee5229cbc6fee9be1de8a62d and 2 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.1, >=4959aebba8c06992abafa09d1e80965e0825af54 <0c716703965ffc5ef4311b65cb5d84a703784717, >=4959aebba8c06992abafa09d1e80965e0825af54 <3e9d89f2ecd3636bd4cbdfd0b2dfdaf58f9882e2, >=4959aebba8c06992abafa09d1e80965e0825af54 <82f9028e83944a9eee5229cbc6fee9be1de8a62d, >=4959aebba8c06992abafa09d1e80965e0825af54 <82fe78065450d2d07f36a22e2b6b44955cf5ca5b, >=4959aebba8c06992abafa09d1e80965e0825af54 <946dec89c41726b94d31147ec528b96af0be1b5a | 0c716703965ffc5ef4311b65cb5d84a703784717, 3e9d89f2ecd3636bd4cbdfd0b2dfdaf58f9882e2, 82f9028e83944a9eee5229cbc6fee9be1de8a62d, 82fe78065450d2d07f36a22e2b6b44955cf5ca5b, 946dec89c41726b94d31147ec528b96af0be1b5a |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket