CVE record · CVE-2026-46207

vsock/virtio: fix empty payload in tap skb for non-linear buffers

No CVSS scoreEPSS 0.0013 · 2nd percentile

Published by the CVE Program (CNA: Linux) at 28 May 2026, 09:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

Affected products, as the CNA wrote them
VendorProductVersions
Linux Linux
  • affected 4b0bf10eb077cb43c09746251ef3608d62c45667 to before 06747f52ab157591cec7e5623a759473b66ef6f6 git
  • affected 4b0bf10eb077cb43c09746251ef3608d62c45667 to before 52da6a74ca3de0fcda60301096b71534b3b18641 git
  • affected 4b0bf10eb077cb43c09746251ef3608d62c45667 to before 378b131a25bd1a5ee27ca199fe486c299d5350c5 git
  • affected 4b0bf10eb077cb43c09746251ef3608d62c45667 to before 3a3e3d90cbc79600544536723911657730759af3 git
Other versions: unaffected
Linux Linux
  • affected 6.7
  • unaffected before 6.7 semver
  • unaffected 6.12.90 to 6.12.*, inclusive semver
  • unaffected 6.18.32 to 6.18.*, inclusive semver
  • unaffected 7.0.9 to 7.0.*, inclusive semver
  • unaffected 7.1 to *, inclusive original_commit_for_fix
Other versions: affected
Identifiers
CVE-2026-46207
CNA
Linux
Published
28 May 2026
Updated
6 Nov 2026

Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS 0.0013, the 2nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 28 May 2026, 09:40 UTC Confirmed by the CVE List
  2. 28 May 2026, 10:16 UTC Confirmed by NVD

Sources

References from the CNA

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.