14 matches found
CVE-2026-82631
A security flaw has been discovered in valkey-io valkey 9.1.0. The affected element is the function handleClientsBlockedOnKey of the file src/blocked.c of the component Blocked-on-keys Subsystem. The manipulation results in use after free. The attack may be performed from remote. A high complexit...
EUVD-2026-68393
A security flaw has been discovered in valkey-io valkey 9.1.0. The affected element is the function handleClientsBlockedOnKey of the file src/blocked.c of the component Blocked-on-keys Subsystem. The manipulation results in use after free. The attack may be performed from remote. A high complexit...
CVE-2026-82631
A use-after-free vulnerability exists in valkey-io valkey 9.1.0 , specifically in the handleClientsBlockedOnKey function within the Blocked-on-keys Subsystem (src/blocked.c). The flaw can be triggered remotely but requires high privileges and carries high attack complexity , limiting practical ex...
CVE-2026-82631 valkey-io valkey Blocked-on-keys blocked.c handleClientsBlockedOnKey use after free
A security flaw has been discovered in valkey-io valkey 9.1.0. The affected element is the function handleClientsBlockedOnKey of the file src/blocked.c of the component Blocked-on-keys Subsystem. The manipulation results in use after free. The attack may be performed from remote. A high complexit...
debugobjects: Do not fill_pool() if pi_blocked_on
...
CVE-2026-53327
In the Linux kernel, the following vulnerability has been resolved: debugobjects: Do not fillpool if piblockedon On RT enabled kernels, fillpool ends up calling rtlocklock, which asserts if current::piblockedon is set, because a task can obviously only block on one lock as otherwise the priority...
CVE-2026-53327
In the Linux kernel, the following vulnerability has been resolved: debugobjects: Do not fillpool if piblockedon On RT enabled kernels, fillpool ends up calling rtlocklock, which asserts if current::piblockedon is set, because a task can obviously only block on one lock as otherwise the priority...
UBUNTU-CVE-2026-53327
In the Linux kernel, the following vulnerability has been resolved: debugobjects: Do not fillpool if piblockedon On RT enabled kernels, fillpool ends up calling rtlocklock, which asserts if current::piblockedon is set, because a task can obviously only block on one lock as otherwise the priority...
CVE-2026-53327
In the Linux kernel, the following vulnerability has been resolved: debugobjects: Do not fillpool if piblockedon On RT enabled kernels, fillpool ends up calling rtlocklock, which asserts if current::piblockedon is set, because a task can obviously only block on one lock as otherwise the priority...
CVE-2026-53327 debugobjects: Do not fill_pool() if pi_blocked_on
In the Linux kernel, the following vulnerability has been resolved: debugobjects: Do not fillpool if piblockedon On RT enabled kernels, fillpool ends up calling rtlocklock, which asserts if current::piblockedon is set, because a task can obviously only block on one lock as otherwise the priority...
EUVD-2026-40961
In the Linux kernel, the following vulnerability has been resolved: debugobjects: Do not fillpool if piblockedon On RT enabled kernels, fillpool ends up calling rtlocklock, which asserts if current::piblockedon is set, because a task can obviously only block on one lock as otherwise the priority...
CVE-2026-53327
Summary: CVE-2026-53327 affects the Linux kernel in the debugobjects path where fill_pool() may interact with rtlock_lock() if current::pi_blocked_on is set on RT-enabled kernels. The connected records confirm concrete remediation across several distributions via patched kernel packages or rootio...
PT-2026-54795
In the Linux kernel, the following vulnerability has been resolved: debugobjects: Do not fill pool if pi blocked on On RT enabled kernels, fill pool ends up calling rtlock lock, which asserts if current::pi blocked on is set, because a task can obviously only block on one lock as otherwise the...
CVE-2026-43499
The CVE-2026-43499 issue concerns the Linux kernel rtmutex path where remove_waiter() operated on current during dequeue in rt_mutex_start_proxy_lock() via futex_requeue(). This caused: (1) rbtree dequeue without waiter::task::pi_lock, (2) waiter task pi_blocked_on not cleared (dangling pointer, ...