Skip to main content
VulnerabilityPublished Updated

CVE-2026-52994: Linux kernel · vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in d0117950075f0a9d5944980784c719d8ebcd4bff : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:49 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in d0117950075f0a9d5944980784c719d8ebcd4bff, 6af1736b5810bc8a4a43a8518530113f5a757dc1, 1cb36e252211506f51095fe7ced8286cc77b4c80

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade Linux kernel to d0117950075f0a9d5944980784c719d8ebcd4bff, 6af1736b5810bc8a4a43a8518530113f5a757dc1 or 1cb36e252211506f51095fe7ced8286cc77b4c80.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 581512a6dc939ef122e49336626ae159f3b8a345, < d0117950075f0a9d5944980784c719d8ebcd4bff
Fixed in
  • d0117950075f0a9d5944980784c719d8ebcd4bff
LinuxLinuxAffected
  • ≥ 581512a6dc939ef122e49336626ae159f3b8a345, < 6af1736b5810bc8a4a43a8518530113f5a757dc1
Fixed in
  • 6af1736b5810bc8a4a43a8518530113f5a757dc1
LinuxLinuxAffected
  • ≥ 581512a6dc939ef122e49336626ae159f3b8a345, < 1cb36e252211506f51095fe7ced8286cc77b4c80
Fixed in
  • 1cb36e252211506f51095fe7ced8286cc77b4c80
LinuxLinuxAffected
  • =6.7
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting virtio_transport_init_zcopy_skb() uses iter->count as the size argument for msg_zerocopy_realloc(), which in turn passes it to mm_account_pinned_pages() for RLIMIT_MEMLOCK accounting. However, this function is called after virtio_transport_fill_skb() has already consumed the iterator via __zerocopy_sg_from_iter(), so on the last skb, iter->count will be 0, skipping the RLIMIT_MEMLOCK enforcement. Pass pkt_len (the total bytes being sent) as an explicit parameter to virtio_transport_init_zcopy_skb() instead of reading the already-consumed iter->count. This matches TCP and UDP, which both call msg_zerocopy_realloc() with the original message size.

References

Community reviews

Loading reviews…