CVE-2026-74310 Affecting kernel-livepatch-6_4_0-150700_7_78-rt package, versions <1-150700.1.3.1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-SLES157-KERNELLIVEPATCH640150700778RT-20935896
- published14 Oct 2026
- disclosed13 Oct 2026
Introduced: 13 Oct 2026
NewCVE-2026-74310 (opens in a new tab)How to fix?
Upgrade SLES:15.7 kernel-livepatch-6_4_0-150700_7_78-rt to version 1-150700.1.3.1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-livepatch-6_4_0-150700_7_78-rt package and not the kernel-livepatch-6_4_0-150700_7_78-rt package as distributed by SLES.
See How to fix? for SLES:15.7 relevant fixed versions and status.
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.
References
- https://www.suse.com/security/cve/CVE-2026-74310.html
- https://bugzilla.suse.com/1276891
- https://git.kernel.org/stable/c/321c73baf54d971ce3771fea275c98a247f7ee35
- https://git.kernel.org/stable/c/6445b945024f4c7675ae5352b2d5885cb1deea71
- https://git.kernel.org/stable/c/8f6898fe80794f2d7c3d38c1158c806e4074a1c4
- https://git.kernel.org/stable/c/a9f8a1d2e3ff511eafd4c5462481950c2f4d2b5d
- https://git.kernel.org/stable/c/c069437924663539a93a1e5afe90838d9ccee284
- https://git.kernel.org/stable/c/ea71f873423fb73e66ad88936d6759ac0ad4aa53