vsock/virtio: Coalesce only linear skb (Linux Linux)

CVE-2026-23057
Not available

At a glance

Source
NVD
EPSS
EPSS 0.20 % · percentile 10 ()
State
PUBLISHED
Published
Updated
Assigner
Linux
NVD status
Deferred

Description

In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: Coalesce only linear skb vsock/virtio common tries to coalesce buffers in rx queue: if a linear skb (with a spare tail room) is followed by a small skb (length limited by GOOD_COPY_LEN = 128), an attempt is made to join them. Since the introduction of MSG_ZEROCOPY support, assumption that a small skb will always be linear is incorrect. In the zerocopy case, data is lost and the linear skb is appended with uninitialized kernel memory. Of all 3 supported virtio-based transports, only loopback-transport is affected. G2H virtio-transport rx queue operates on explicitly linear skbs; see virtio_vsock_alloc_linear_skb() in virtio_vsock_rx_fill(). H2G vhost-transport may allocate non-linear skbs, but only for sizes that are not considered for coalescence; see PAGE_ALLOC_COSTLY_ORDER in virtio_vsock_alloc_skb(). Ensure only linear skbs are coalesced. Note that skb_tailroom(last_skb) > 0 guarantees last_skb is linear.

References

European references

CERT-FR advisories

Affected products

ProductVersions
Linux · Linuxaffected 581512a6dc939ef122e49336626ae159f3b8a345 < 568e9cd8ed7ca9bf748c7687ba6501f29d30e59f ; affected 581512a6dc939ef122e49336626ae159f3b8a345 < 63ef9b300bd09e24c57050c5dbe68feedce42e72 ; affected 581512a6dc939ef122e49336626ae159f3b8a345 < 0386bd321d0f95d041a7b3d7b07643411b044a96
Linux · Linuxaffected 6.7 ; unaffected 0 < 6.7 ; unaffected 6.12.68 ≤ 6.12.* ; unaffected 6.18.8 ≤ 6.18.* ; unaffected 6.19 ≤ *

Sources

SourceLicence
CVE List (CVEProject cvelistV5)CVE Program Terms of Use
EPSS (FIRST.org)FIRST — attribution requested
ENISA EUVDENISA — reproduction authorised, source acknowledged
CERT-FR (ANSSI)Licence Ouverte / Etalab 2.0
NVD (NIST) via fkie-cad/nvd-json-data-feedsPublic domain — this product uses data from the NVD API but is not endorsed or certified by the NVD