CVE-2026-82631

A flaw was found in Valkey. A use-after-free vulnerability exists within the handleClientsBlockedOnKey function of the Blocked-on-keys Subsystem. A remote attacker could exploit this flaw, leading to a denial of service. The complexity of exploiting this vulnerability is high...

AZL-98439 CVE-2026-82631 affecting package valkey for versions less than 8.0.11-1

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 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...

UBUNTU-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 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...

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...

PT-2026-83717

Name of the Vulnerable Software and Affected Versions valkey-io valkey version 9.1.0 Description A use after free flaw exists in the Blocked-on-keys Subsystem within the handleClientsBlockedOnKey function located in the src/blocked.c file. This issue can be triggered remotely, although the attack...

Linux Distros Unpatched Vulnerability : CVE-2026-82631

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - 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...

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

Name of the Vulnerable Software and Affected Versions Linux kernel affected versions not specified Description In RT enabled kernels, the fill pool function calls rtlock lock, which triggers an assertion if the pi blocked on variable is set. This occurs because a task can only block on one lock t...

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, ...