virtio-net: fix len check in receive_big()
Summary
| CVE | CVE-2026-64552 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-07-27 21:17:08 UTC |
|---|
| Updated | 2026-07-27 21:17:08 UTC |
|---|
| Description | In the Linux kernel, the following vulnerability has been resolved:
virtio-net: fix len check in receive_big()
receive_big() bounds the device-announced length by
(big_packets_num_skbfrags + 1) * PAGE_SIZE. That is still too loose:
add_recvbuf_big() sets sg[1] to start at offset
sizeof(struct padded_vnet_hdr) into the first page, so the chain
actually carries hdr_len + (PAGE_SIZE - sizeof(padded_vnet_hdr)) +
big_packets_num_skbfrags * PAGE_SIZE bytes -- 20 bytes less than the
check allows for the common hdr_len == 12 case.
A malicious virtio backend can announce a len in that gap. page_to_skb()
then walks one frag past the page chain, storing a NULL page->private
into skb_shinfo()->frags[MAX_SKB_FRAGS], which is both an out-of-bounds
write past the static frag array and a NULL frag handed up the rx path.
Bound len by the size add_recvbuf_big() actually advertised. |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 82f9028e83944a9eee5229cbc6fee9be1de8a62d f9451d0fd5ba635dcabb49bfe456a6db734a8986 git |
Not specified |
| CNA |
Linux |
Linux |
affected 946dec89c41726b94d31147ec528b96af0be1b5a 38e94d63e29f4a5c6eae87ee2c02101aaa321502 git |
Not specified |
| CNA |
Linux |
Linux |
affected 82fe78065450d2d07f36a22e2b6b44955cf5ca5b fbeb65154583879d556ea94cb2f15888e9470f3d git |
Not specified |
| CNA |
Linux |
Linux |
affected 0c716703965ffc5ef4311b65cb5d84a703784717 c7fc9adf4e006155f7f2aeda052fbcde25cdcc49 git |
Not specified |
| CNA |
Linux |
Linux |
affected 0c716703965ffc5ef4311b65cb5d84a703784717 e6b8463b7d791f3886d7584259d6e9f06a69f12e git |
Not specified |
| CNA |
Linux |
Linux |
affected 0c716703965ffc5ef4311b65cb5d84a703784717 9e5ad06ea826322ce8c58b4a68442a96f600c3c4 git |
Not specified |
| CNA |
Linux |
Linux |
affected 3e9d89f2ecd3636bd4cbdfd0b2dfdaf58f9882e2 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.1.159 6.1.178 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.6.117 6.6.145 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.12.58 6.12.97 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.17.8 6.18 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.18 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.178 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.145 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.97 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.40 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.5 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/9e5ad06ea826322ce8c58b4a68442a96f600c3c4 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/38e94d63e29f4a5c6eae87ee2c02101aaa321502 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/e6b8463b7d791f3886d7584259d6e9f06a69f12e |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/f9451d0fd5ba635dcabb49bfe456a6db734a8986 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/fbeb65154583879d556ea94cb2f15888e9470f3d |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/c7fc9adf4e006155f7f2aeda052fbcde25cdcc49 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.