CVE-2026-64552

virtio-net: fix len check in receive_big()

HIGH
8.4
CVSS Score
Published: July 27, 2026 at 08:10 PM UTC
Updated: October 19, 2026 at 09:17 PM UTC
4 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 CPU 1518-4 Pn /dp MFP FirmwareSiplus S7-1500 CPU 1518-4 Pn /dp MFP Firmware

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.1%
SSVC
No known exploit

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.

Affected

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

0c716703965ffc5ef4311b65cb5d84a7037847173e9d89f2ecd3636bd4cbdfd0b2dfdaf58f9882e26.1.1596.12.586.17.86.186.6.11782f9028e83944a9eee5229cbc6fee9be1de8a62d82fe78065450d2d07f36a22e2b6b44955cf5ca5b946dec89c41726b94d31147ec528b96af0be1b5a
Vendor states this is fixed in 38e94d63e29f4a5c6eae87ee2c02101aaa321502 (fixed)
Vendor states this is fixed in 9e5ad06ea826322ce8c58b4a68442a96f600c3c4 (fixed)
Vendor states this is fixed in c7fc9adf4e006155f7f2aeda052fbcde25cdcc49 (fixed)
Vendor states this is fixed in e6b8463b7d791f3886d7584259d6e9f06a69f12e (fixed)
Vendor states this is fixed in f9451d0fd5ba635dcabb49bfe456a6db734a8986 (fixed)
Vendor states this is fixed in fbeb65154583879d556ea94cb2f15888e9470f3d (fixed)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (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

StatusRECEIVED
CWE
CWE-787

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