Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-74310vhost/net: complete zerocopy ubufs only once

Description

In the Linux kernel, the following vulnerability has been resolved: vhost/net: complete zerocopy ubufs only once vhost-net initializes one ubuf_info per outstanding zerocopy TX descriptor and hands it to the backend socket. The networking stack may then clone a zerocopy skb before all skb references are released. For example, batman-adv fragmentation reaches skb_split(), which calls skb_zerocopy_clone() and increments the same ubuf_info refcount. vhost_zerocopy_complete() currently treats every ubuf callback as a completed vhost descriptor. It dereferences ubuf->ctx, writes the descriptor completion state, and drops the vhost_net_ubuf_ref even when the callback only releases a cloned skb reference. A backend reset can therefore wait for and free the vhost_net_ubuf_ref while another cloned skb still carries the same ubuf_info. A later completion then dereferences the freed ubufs pointer. KASAN reports the stale completion as: BUG: KASAN: slab-use-after-free in vhost_zerocopy_complete+0x1d7/0x1f0 BUG: KASAN: slab-use-after-free in vhost_zerocopy_complete+0x101/0x1f0 vhost_zerocopy_complete skb_copy_ubufs __dev_forward_skb2 veth_xmit The freed object was allocated from vhost_net_ioctl() while setting the backend and freed through kfree_rcu()/kvfree_rcu_bulk after backend removal, while delayed skb completion still reached vhost_zerocopy_complete(). Honor the generic ubuf_info refcount before touching vhost state, and run the vhost descriptor completion only for the final ubuf reference. This matches the msg_zerocopy_complete() ownership rule for cloned zerocopy skbs.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-74310, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.3CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NVDNVD · Received3.1Critical9.3CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (20 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.3.

Affected products

  • Linux · Linux

    • affected bab632d69ee48a106e779b60cc01adfe80a72807 – < ea71f873423fb73e66ad88936d6759ac0ad4aa53
    • affected bab632d69ee48a106e779b60cc01adfe80a72807 – < 6445b945024f4c7675ae5352b2d5885cb1deea71
    • affected bab632d69ee48a106e779b60cc01adfe80a72807 – < a9f8a1d2e3ff511eafd4c5462481950c2f4d2b5d
    • affected bab632d69ee48a106e779b60cc01adfe80a72807 – < 321c73baf54d971ce3771fea275c98a247f7ee35
    • affected bab632d69ee48a106e779b60cc01adfe80a72807 – < c069437924663539a93a1e5afe90838d9ccee284
    • affected bab632d69ee48a106e779b60cc01adfe80a72807 – < 8f6898fe80794f2d7c3d38c1158c806e4074a1c4
  • Linux · Linux

    • affected 3.1
    • unaffected < 3.1
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74310 badge
[![CVE-2026-74310](https://cveledger.app/badge/CVE-2026-74310.svg)](https://cveledger.app/cve/CVE-2026-74310)

Record last updated .