EUVD-2026-59625

In the Linux kernel, the following vulnerability has been resolved: xsk: fix buffer leak in xskdropskb for AFXDP multi-buffer Tx This patch is inspired by the check1 from sashiko. It says when overflow happens, the address of cq to be published is invalid. Actually the severer thing is the whole...

CVE-2026-74560

CVE-2026-74560 concerns the Linux kernel XDP stack, specifically the xsk_drop_skb() path for AF_XDP multi-buffer transmissions. The issue arises when an overflow path partially builds multi-fragment skbs, causing buffer addresses to be published incorrectly and leaving buffers untracked in usersp...

SUSE CVE-2026-23048

In the Linux kernel, the following vulnerability has been resolved: udp: call skborphan before skbattemptdeferfree Standard UDP receive path does not use skb-destructor. But skmsg layer does use it, since it calls skbsetownersksafe from udpreadskb. This then triggers this warning in...

CVE-2026-23048

In the Linux kernel, the following vulnerability has been resolved: udp: call skborphan before skbattemptdeferfree Standard UDP receive path does not use skb-destructor. But skmsg layer does use it, since it calls skbsetownersksafe from udpreadskb. This then triggers this warning in...

CVE-2026-23048

The CVE-2026-23048 entry describes a Linux kernel UDP path issue: the standard UDP receive path did not use skb->destructor, while the skmsg layer did via skb_set_owner_sk_safe() in udp_read_skb(), leading to a DEBUG_NET_WARN_ON_ONCE(skb->destructor) in skb_attempt_defer_free(). The documen...

EUVD-2026-5499

In the Linux kernel, the following vulnerability has been resolved: udp: call skborphan before skbattemptdeferfree Standard UDP receive path does not use skb-destructor. But skmsg layer does use it, since it calls skbsetownersksafe from udpreadskb. This then triggers this warning in...

PT-2026-6118

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description The Linux kernel contains an issue where the standard UDP receive path does not utilize skb-destructor, but the skmsg layer does through a call to skb set owner sk safe from udp read skb...