CVE-2026-68137

The CVE-2026-68137 entry concerns the Linux kernel net/x25 subsystem and a use-after-free in x25_kill_by_neigh(). The flaw arises when walking the global X.25 socket list under x25_list_lock and then dropping the lock before locking the socket with lock_sock(s). A concurrent close can remove the ...

EUVD-2026-55518

In the Linux kernel, the following vulnerability has been resolved: net/x25: fix use-after-free in x25killbyneigh x25killbyneigh walks the global X.25 socket list looking for sockets attached to a terminating neighbour. x25listlock protects list membership while the lookup is in progress, but it...

CVE-2026-68137 net/x25: fix use-after-free in x25_kill_by_neigh()

In the Linux kernel, the following vulnerability has been resolved: net/x25: fix use-after-free in x25killbyneigh x25killbyneigh walks the global X.25 socket list looking for sockets attached to a terminating neighbour. x25listlock protects list membership while the lookup is in progress, but it...

CVE-2026-68137

In the Linux kernel, the following vulnerability has been resolved: net/x25: fix use-after-free in x25killbyneigh x25killbyneigh walks the global X.25 socket list looking for sockets attached to a terminating neighbour. x25listlock protects list membership while the lookup is in progress, but it...

EUVD-2026-55517

In the Linux kernel, the following vulnerability has been resolved: net: gro: fix double aggregation of flush-marked skbs Commit 0ab03f353d36 "net-gro: Fix GRO flush when receiving a GSO packet." added a flush check to skbgroreceive, but skbgroreceivelist lacks the same validation. As a result,...

CVE-2026-68136

In the Linux kernel CVE-2026-68136, the vulnerability stems from net: gro where skb_gro_receive_list() lacked a flush validation present in skb_gro_receive(), allowing already-GRO’d packets with a frag_list to be re-aggregated into a new GRO session. This can corrupt the frag_list chain and lead ...

CVE-2026-68136 net: gro: fix double aggregation of flush-marked skbs

In the Linux kernel, the following vulnerability has been resolved: net: gro: fix double aggregation of flush-marked skbs Commit 0ab03f353d36 "net-gro: Fix GRO flush when receiving a GSO packet." added a flush check to skbgroreceive, but skbgroreceivelist lacks the same validation. As a result,...

CVE-2026-68136

In the Linux kernel, the following vulnerability has been resolved: net: gro: fix double aggregation of flush-marked skbs Commit 0ab03f353d36 "net-gro: Fix GRO flush when receiving a GSO packet." added a flush check to skbgroreceive, but skbgroreceivelist lacks the same validation. As a result,...

CVE-2026-68135

In the Linux kernel, the following vulnerability has been resolved: net: hip04: fix RX buffer leak on buildskb failure When buildskb fails in hip04rxpoll, the driver jumps to the refill path without releasing the current RX buffer and its DMA mapping. Installing a replacement buffer then overwrit...

CVE-2026-68135 net: hip04: fix RX buffer leak on build_skb failure

In the Linux kernel, the following vulnerability has been resolved: net: hip04: fix RX buffer leak on buildskb failure When buildskb fails in hip04rxpoll, the driver jumps to the refill path without releasing the current RX buffer and its DMA mapping. Installing a replacement buffer then overwrit...

EUVD-2026-55516

In the Linux kernel, the following vulnerability has been resolved: net: hip04: fix RX buffer leak on buildskb failure When buildskb fails in hip04rxpoll, the driver jumps to the refill path without releasing the current RX buffer and its DMA mapping. Installing a replacement buffer then overwrit...

CVE-2026-68135 net: hip04: fix RX buffer leak on build_skb failure

In the Linux kernel, the following vulnerability has been resolved: net: hip04: fix RX buffer leak on buildskb failure When buildskb fails in hip04rxpoll, the driver jumps to the refill path without releasing the current RX buffer and its DMA mapping. Installing a replacement buffer then overwrit...

EUVD-2026-55515

In the Linux kernel, the following vulnerability has been resolved: ptp: ptps390: Add missing facility check Only register the physical clock when facility 28 is installed and PTFF QAF returns that PTFF QPT is available...

CVE-2026-68134

In the Linux kernel, the following vulnerability has been resolved: ptp: ptps390: Add missing facility check Only register the physical clock when facility 28 is installed and PTFF QAF returns that PTFF QPT is available...

CVE-2026-68134 ptp: ptp_s390: Add missing facility check

In the Linux kernel, the following vulnerability has been resolved: ptp: ptps390: Add missing facility check Only register the physical clock when facility 28 is installed and PTFF QAF returns that PTFF QPT is available...

CVE-2026-68134

CVE-2026-68134 pertains to the Linux kernel, specifically the ptp_s390 driver. The issue arises from a missing facility check when registering the physical clock, which could occur unless facility 28 is installed and PTFF QAF indicates that PTFF QPT is available. The fix adds the required facilit...

EUVD-2026-55514

In the Linux kernel, the following vulnerability has been resolved: ice: fix PTP Call Trace during PTP release If a PF reset occurs when the PTP state is ICEPTPUNINIT, then iceptprebuild will update the state to ICEPTPERROR. This will result in the following PTP release call trace during driver...

CVE-2026-68133 ice: fix PTP Call Trace during PTP release

In the Linux kernel, the following vulnerability has been resolved: ice: fix PTP Call Trace during PTP release If a PF reset occurs when the PTP state is ICEPTPUNINIT, then iceptprebuild will update the state to ICEPTPERROR. This will result in the following PTP release call trace during driver...

CVE-2026-68133

In the Linux kernel, the following vulnerability has been resolved: ice: fix PTP Call Trace during PTP release If a PF reset occurs when the PTP state is ICEPTPUNINIT, then iceptprebuild will update the state to ICEPTPERROR. This will result in the following PTP release call trace during driver...

CVE-2026-68132

CVE-2026-68132 concerns the Linux kernel thaw deadlock involving frozen block devices. The root cause is do_thaw_all_callback() calling bdev_thaw() while holding sb->s_umount, which can lead to a deadlock when a block device frozen via bdev_freeze() drops the last freeze reference and fs_bdev_...