The vulnerability originates in the Linux kernel’s dm-cache module when operating in passthrough mode. During cache entry invalidation, a concurrent write to the same block can cause a lock failure, leaving a pointer null. The error path then attempts to unlock and free this null pointer, leading to a kernel panic or system hang. This null‑pointer dereference does not directly provide remote code execution, but may cause system instability. The possibility that an attacker could exploit such instability for privilege escalation or persistence is inferred from the description and is not explicitly stated in the CVE data.

This flaw affects the Linux Kernel, specifically any release that includes the unpatched dm-cache implementation. There are no explicit version numbers listed in the CVE data, suggesting that the issue existed in versions up to at least 6.19.0-rc7. All systems running a vulnerable kernel that enable dm-cache in passthrough mode are impacted.

The CVSS score is not provided in the data, and no EPSS score is available, so the exact exploitation probability cannot be quantified. The write operations required for reproduction involve local access to block devices and the use of tools such as fio. This indicates that the exploit requires local or privileged access, but this inference is based on the reproduction steps and is not explicitly stated in the CVE description. The kernel panic can theoretically be triggered by any process capable of performing concurrent writes; however, this is an inference from the issue context rather than an explicit statement. While it does not facilitate immediate remote code execution, repeated or sustained kernel crashes can be effectively used for denial of service. The vulnerability is not listed in the CISA KEV catalog, so official exploitation reports are not available yet.