232380 matches found
SUSE CVE-2026-64009
In the Linux kernel, the following vulnerability has been resolved: xfrm: Check for underflow in xfrmstatemtu Leo Lin reported OOB write issue in esp component: xfrmstatemtu returns u32 but performs its arithmetic in unsigned modulo-2^32 space using an attacker-influenced "headerlen + authsize +...
SUSE CVE-2026-64010
In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: Fix use-after-free race in nfcllcprecvcc A race condition exists in the NFC LLCP connection state machine where the connection acceptance packet CC can be processed concurrently with socket release. This can lead to a...
SUSE CVE-2026-64011
In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: Fix use-after-free in llcpsockrelease llcpsockrelease unconditionally unlinks the socket from the local sockets list. However, if the socket is still in connecting state, it is on the connecting list. Fix this by...
SUSE CVE-2026-64012
In the Linux kernel, the following vulnerability has been resolved: net/sched: schsfb: Replace direct dequeue call with peek and qdiscdequeuepeeked When sfb has children eg qfq qdisc whose peek callback is qdiscpeekdequeued, we could get a kernel panic. When the parent of such qdiscs eg illustrat...
SUSE CVE-2026-64015
In the Linux kernel, the following vulnerability has been resolved: security/keys: fix missed RCU read section on lookup Nicholas Carlini reports that the keyring code calls assocarrayfind in findkeytoupdate without holding the RCU read lock, while the assocarraygc code really is designed around...
SUSE CVE-2026-64016
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix durable reconnect error path file lifetime After a durable reconnect succeeds, ksmbdreopendurablefd republishes the same ksmbdfile into the session volatile-id table. If smb2open then takes a later error path, cleanup...
SUSE CVE-2026-64020
In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix dmavecs leak on p2p memory We don't unmap P2P memory, so we don't need to track it. The dmavec allocation was getting leaked on the completion...
SUSE CVE-2026-64021
In the Linux kernel, the following vulnerability has been resolved: drm/xe/oa: Fix execqueue leak on width check in stream open In xeoastreamopenioctl, when param.execq-width 1 the function returns -EOPNOTSUPP directly, skipping the existing errexecq cleanup path. The execqueue reference obtained...
SUSE CVE-2026-64022
In the Linux kernel, the following vulnerability has been resolved: gpio: aggregator: remove the software node when deactivating the aggregator The dynamic software node we create for the aggregator platform device when using configfs is leaked when the device is deactivated. Destroy it as the la...
SUSE CVE-2026-64023
In the Linux kernel, the following vulnerability has been resolved: gpio: aggregator: fix a potential use-after-free On error we free aggr-lookups-devid before removing the entry from the lookup table. If a concurrent thread calls gpiodfind before we remove the entry, it could iterate over the li...
SUSE CVE-2026-64024
In the Linux kernel, the following vulnerability has been resolved: tcp: fix stale per-CPU tcptwisn leak enabling ISN prediction Blamed commit moved the TIMEWAIT-derived ISN from the skb control block to a per-CPU variable, assuming the value would always be consumed by tcpconnrequest for the sam...
SUSE CVE-2026-64025
In the Linux kernel, the following vulnerability has been resolved: bpf, skmsg: fix verdict skdataready racing with ktls rx skpsockstrpdataready already checks tlsswhasctxrx and defers to psock-saveddataready when a TLS RX context is present, avoiding a conflict with the TLS strparser's ownership...
SUSE CVE-2026-64027
In the Linux kernel, the following vulnerability has been resolved: net: shaper: rework the VALID marking again Recent commit changed the semantics from NOTVALID to VALID. I didn't realize that the flags are not stored atomically with the entry in XArray. There's still a race of reader observing ...
SUSE CVE-2026-64028
In the Linux kernel, the following vulnerability has been resolved: tracing: Avoid NULL return from histfieldname on truncation histfieldname returns "" everywhere except the fully-qualified VARREF/EXPR case, where snprintf truncation returns NULL early and bypasses the bottom NULL-"" guard...
SUSE CVE-2026-64029
In the Linux kernel, the following vulnerability has been resolved: ALSA: seq: Serialize UMP output teardown with eventinput sequmpprocessevent borrows client-outrfile.output without synchronizing with the first-open and last-close transition in sequmpclientopen and sequmpclientclose. The last...
SUSE CVE-2026-64032
In the Linux kernel, the following vulnerability has been resolved: bridge: mcast: Fix a possible use-after-free when removing a bridge port When per-VLAN multicast snooping is enabled, the bridge iterates over all the bridge ports, disables the per-port multicast context on each port and enables...
SUSE CVE-2026-64033
In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs: Fix use-after-free in path file creation cleanup In the error path of rtrssrvcreatepathfiles, the sysfs root folders may already have been created and srvpath-kobj may already have been initialized. If a later step...
SUSE CVE-2026-64034
In the Linux kernel, the following vulnerability has been resolved: net: mana: Fix TOCTOU double-fetch of hwcmsgid from DMA buffer In manahwcrxeventhandler, resp-response.hwcmsgid is read from DMA-coherent memory and bounds-checked, then manahwchandleresp re-reads the same field from the same DMA...
CVE-2026-63966
A flaw was found in the Linux kernel's adis16550 Industrial Input/Output IIO Inertial Measurement Unit IMU driver. The adis16550triggerhandler function fails to fully initialize a stack-allocated data array. This oversight allows uninitialized stack memory to be exposed to userspace, leading to...
CVE-2026-63904
A flaw was found in the Linux kernel's USB Test and Measurement Class USBTMC driver. This vulnerability occurs because the driver does not properly verify the size of incoming notification messages, specifically failing to ensure that required two-byte headers are present. An attacker could explo...