In the Linux kernel memory allocator, the counter used to protect slab allocations—current->mems_allowed_seq—is accessed during a hard interrupt (NMI) even though it is not NMI‑safe. The lockdep diagnostics report an inconsistent lock state and a potential deadlock, which can lead to a kernel panic. The vulnerability results from improper locking around a sequence counter that is not designed for use in an NMI context.

The flaw is present in the Linux mm/slab code path and has been observed in development kernel releases such as 6.19.0‑rc5. Systems running these or earlier kernels that have not incorporated the fix are affected; the CVE does not list a specific version range but references commits that address the issue in the 6.19 series and earlier snapshots.

The EPSS score is less than 1%, indicating a very low probability of exploitation. The CVSS score of 5.5 reflects medium severity. Nonetheless the impact is high if exploited: a triggered NMI or interrupt that re‑enters the slab allocator can cause a deadlock or crash the kernel. The most likely attack vector is the deliberate or accidental generation of NMIs to exercise the unsafe access path; however, no public exploit has been disclosed.