The Linux kernel contains a race condition in the slab allocator where concurrent allocation and deallocation of objects can cause the internal free list to become corrupted. This ABA problem occurs when a CPU frees an object, causing the slab to be added to the partial list, and another CPU concurrently allocates from the same slab while the slab is being removed. The missing synchronization results in list_add corruption and a kernel panic, producing a system crash that disrupts all operations and can lead to data loss.

All Linux kernel builds that contain the buggy slab allocator code are affected. The vendor listed is Linux; the product is the Linux kernel. No specific version numbers are enumerated, but any kernel prior to the commit that re‑locks around the slab list manipulation is at risk.

The CVSS score is not provided and EPSS is unavailable, indicating no current quantified risk assessment. The vulnerability is not in the CISA KEV catalog. Exploitation requires a multi‑CPU environment and a workload that heavily exercises the slab allocator. While the race condition is nondeterministic and the exploit path is non‑trivial, the consequence of a kernel panic makes the risk high for systems still running vulnerable kernels. Given the lack of public exploits, the problem remains theoretical but should be remediated proactively.