4609 matches found
kernel: RDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()
A flaw was found in the Linux kernel's RDMA/mana component. A local user could trigger a kernel corruption by providing specific configurations through the user Application Programming Interface uAPI that cause an internal error. This issue arises when Work Queues WQs are specified to share the...
kernel: RDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss()
A flaw was found in the Linux kernel's RDMA/mana component. A local user could trigger a kernel corruption by providing specific configurations through the user Application Programming Interface uAPI that cause an internal error. This issue arises when Work Queues WQs are specified to share the...
EUVD-2026-42329
Mistune plugins/formatting: quadratic-time parsing on long runs of x, ==x==, and ^^x^^ markers strikethrough / mark / insert...
CVE-2026-64206
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: cancel pendingrxwork before taking conn-lock l2capconndel takes conn-lock and then calls cancelworksync for pendingrxwork. processpendingrx takes the same mutex, so teardown can deadlock against the worker it is...
CVE-2026-64073
A flaw was found in the Linux kernel, specifically within the irqwork subsystem when running on systems configured with PREEMPTRT. This vulnerability is a use-after-free, where the system attempts to access memory after it has been released. A local attacker could exploit this timing issue to cau...
EUVD-2026-46014
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: cancel pendingrxwork before taking conn-lock l2capconndel takes conn-lock and then calls cancelworksync for pendingrxwork. processpendingrx takes the same mutex, so teardown can deadlock against the worker it is...
CVE-2026-64206 Bluetooth: L2CAP: cancel pending_rx_work before taking conn->lock
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: cancel pendingrxwork before taking conn-lock l2capconndel takes conn-lock and then calls cancelworksync for pendingrxwork. processpendingrx takes the same mutex, so teardown can deadlock against the worker it is...
CVE-2026-64206
CVE-2026-64206 : In the Linux kernel Bluetooth L2CAP path, the teardown can deadlock because l2cap_conn_del() takes conn->lock and then cancels pending_rx_work, while process_pending_rx() also takes the same lock. The fix is to cancel pending_rx_work before acquiring conn->lock to enforce t...
SUSE CVE-2026-53399
In the Linux kernel, the following vulnerability has been resolved: nfsd: release layout stid on setlease failure nfs4allocstid publishes the new stid into cl-clstateids via idralloccyclic under cllock before returning to nfsd4alloclayoutstateid. When nfsd4layoutsetlease then fails, the error pat...
CVE-2026-64148
In the Linux kernel, the following vulnerability has been resolved: pdscore: fix error handling in pdscdevcmdwait Fix two cases where pdscdevcmdwait returns stale success from the completion register instead of an error: 1. FW crash: If firmware stops running, the wait loop breaks early with...
CVE-2026-64073
In the Linux kernel, the following vulnerability has been resolved: irqwork: Fix use-after-free in irqworksingle on PREEMPTRT On PREEMPTRT, non-HARD irqwork runs in per-CPU kthreads via runirqworkd, so irqworksync uses rcuwait to wait for BUSY==0. After irqworksingle clears BUSY via atomiccmpxchg...
EUVD-2026-45833
In the Linux kernel, the following vulnerability has been resolved: pdscore: fix error handling in pdscdevcmdwait Fix two cases where pdscdevcmdwait returns stale success from the completion register instead of an error: 1. FW crash: If firmware stops running, the wait loop breaks early with...
CVE-2026-64112
The CVE-2026-64112 issue affects the Linux kernel’s RBD path (rbd_lock_add_request/rbd_img_exclusive_lock) where lock_dwork can be (re)queued more than needed, enabling a TOCTOU race during image unmapping. The problem arises when a new I/O request arrives during rbd_acquire_lock(), or in maybe_k...
CVE-2026-64108
The CVE-2026-64108 entry documents a Linux kernel CIFS issue where a cifs file close work (cfile->deferred) could run after unmount, leaving a dentry still in use during shutdown. Root cause: after dentry ref counting changes, the deferred close may execute post-unmount, triggering a warning i...
CVE-2026-64108 cifs: Fix busy dentry used after unmounting
In the Linux kernel, the following vulnerability has been resolved: cifs: Fix busy dentry used after unmounting Since commit 340cea84f691c "cifs: open files should not hold ref on superblock", cifs file only holds the dentry refcnt, the cifs file close workcfile-deferred could be executed after...
CVE-2026-64108
In the Linux kernel, the following vulnerability has been resolved: cifs: Fix busy dentry used after unmounting Since commit 340cea84f691c "cifs: open files should not hold ref on superblock", cifs file only holds the dentry refcnt, the cifs file close workcfile-deferred could be executed after...
EUVD-2026-45646
In the Linux kernel, the following vulnerability has been resolved: irqwork: Fix use-after-free in irqworksingle on PREEMPTRT On PREEMPTRT, non-HARD irqwork runs in per-CPU kthreads via runirqworkd, so irqworksync uses rcuwait to wait for BUSY==0. After irqworksingle clears BUSY via atomiccmpxchg...
CVE-2026-64073
Summary of CVE-2026-64073 (Linux kernel): A use-after-free in irq_work_single() on PREEMPT_RT was fixed. On PREEMPT_RT, non-HARD irq_work runs in per-CPU kthreads via run_irq_workd(), and irq_work_sync() uses rcuwait() to wait for BUSY==0. After irq_work_single() clears BUSY with atomic_cmpxchg()...
CVE-2026-64073 irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT
In the Linux kernel, the following vulnerability has been resolved: irqwork: Fix use-after-free in irqworksingle on PREEMPTRT On PREEMPTRT, non-HARD irqwork runs in per-CPU kthreads via runirqworkd, so irqworksync uses rcuwait to wait for BUSY==0. After irqworksingle clears BUSY via atomiccmpxchg...
CVE-2026-64073 irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT
In the Linux kernel, the following vulnerability has been resolved: irqwork: Fix use-after-free in irqworksingle on PREEMPTRT On PREEMPTRT, non-HARD irqwork runs in per-CPU kthreads via runirqworkd, so irqworksync uses rcuwait to wait for BUSY==0. After irqworksingle clears BUSY via atomiccmpxchg...