PT-2026-90762

Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time,...

PT-2026-90739

Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time,...

PT-2026-90748

Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time,...

PT-2026-90751

Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time,...

CVE-2026-78662: Allocation of Resources Without Limits or Throttling

Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time,...

PT-2026-90734

Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time,...

PT-2026-90741

Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time,...

PT-2026-90749

Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time,...

PT-2026-90756

Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time,...

PT-2026-90760

Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time,...

PT-2026-90745

Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time,...

CVE-2026-78662: Allocation of Resources Without Limits or Throttling

Previously, a channel registered in the mux's chanList is not usable until it is established. A malicious peer was able flood the channel's incomingRequests, deadlocking the entire connection. Now, we add an atomic established state, set when a channel becomes usable. Until such a time,...

SUSE CVE-2026-72187

In the Linux kernel, the following vulnerability has been resolved: ntfs: avoid self-deadlock during inode eviction An attribute-list update performed while allocating clusters can drop the last reference to the temporary attribute inode. Evicting that inode drops its reference to the base inode...

SUSE CVE-2026-72189

In the Linux kernel, the following vulnerability has been resolved: ntfs: fail attrlist updates when the superblock is inactive genericshutdownsuper clears SBACTIVE before evicting cached inodes. If eviction selects the fake inode for a base inode's unnamed $ATTRIBUTELIST attribute,...

SUSE CVE-2026-72190

In the Linux kernel, the following vulnerability has been resolved: ntfs: fix mreclock ABBA deadlock in rename ntfsfilefsync, ntfsdirfsync and ntfswriteinode lock an inode's mreclock before taking the mreclock of its parent directory. ntfsrename takes oldni-mreclock and olddirni-mreclock before...

SUSE CVE-2026-72314

In the Linux kernel, the following vulnerability has been resolved: regulator: core: regulatorlocktwo should test for EDEADLK not EDEADLOCK Compare against -EDEADLK, which is what wwmutexlock actually returns and what every other deadlock check in this file already uses. Function regulatorlocktwo...

SUSE CVE-2026-72332

In the Linux kernel, the following vulnerability has been resolved: accel/amdxdna: Prevent PM resume deadlock in hwctxsyncdebugbo amdxdnahwctxsyncdebugbo invokes the hardware hwctxsyncdebugbo callback while holding xdna-devlock. The callback may call amdxdnacmdsubmit, which in turn calls...

CVE-2026-80687

A flaw was found in the Linux kernel's iommufd/viommu component. An error in the iommufdvdeviceallocioctl function's error handling path can lead to a lock being held indefinitely. This can cause a deadlock, preventing further virtual device vDEVICE operations and resulting in a Denial of Service...

CVE-2026-80666

A flaw was found in the Linux kernel's Bluetooth Synchronous Connection-Oriented SCO component. A race condition exists in the scosocktimeout function. When a Bluetooth SCO socket is closing while its timer is active, the system attempts to acquire the same lock twice, leading to a deadlock. This...

CVE-2026-80659

A flaw was found in the Linux kernel's vub300 driver. When the vub300cmndworkthread function holds a command mutex and a command response times out, the device reset path attempts to re-acquire the same mutex recursively. This recursive locking can lead to a deadlock, causing a Denial of Service...