The Linux kernel bug involves the routine fill_pool() used during memory pool management. When run on a real‑time enabled kernel, fill_pool() calls rtlock_lock() without first verifying whether the current task is already blocked on a priority‑inheritance lock (the current::pi_blocked_on flag). If the flag is set, rtlock_lock() triggers an assertion failure, which causes a kernel panic and an abrupt system crash, effectively denying service. This weakness is a form of state corruption leading to an invalid assertion."

All Linux kernel builds that are compiled with CONFIG_DEBUG_OBJECTS and enable real‑time preemption (CONFIG_PREEMPT_RT=y) are vulnerable unless they incorporate commit 33bee106 that adds the missing guard on current::pi_blocked_on. Distributions that have not applied this upstream commit, or that still ship older kernel versions, are therefore at risk.

The flaw does not provide an external attack vector. An attacker would need to execute code in kernel mode or otherwise gain privileged control to reproduce the panic scenario. The CVSS score of 5.5 reflects a moderate impact given the denial‑of‑service nature of the kernel crash. The EPSS score of less than 1% indicates a very low probability of exploitation in the wild, and the vulnerability is not listed in the CISA KEV catalog, suggesting no known active exploitation.