A flaw in the Linux kernel blktrace subsystem occurs when the per‑CPU helpers __this_cpu_read() and __this_cpu_write() are called while preemption is enabled. These helpers are only safe in scheduler context, and their use in process context triggers a BUG that can cause a kernel panic. Based on the description, we infer that the vulnerability does not provide remote code execution or information disclosure; its primary impact is loss of availability through a crash. The weakness corresponds to data‑structure integrity failure (CWE‑820).

All Linux kernel releases compiled with the default blktrace configuration that predate the patch are affected. The fix was demonstrated in kernel 7.0.0‑rc1 and earlier, but the issue applies to any kernel version that still contains the unguarded __this_cpu_read/write calls inside the blktrace tracing paths. No specific distribution or vendor is singled out; the problem exists in the upstream Linux kernel itself.

The CVSS score of 5.5 indicates moderate severity, while the EPSS score of less than 1% suggests a low likelihood of exploitation. The vulnerability is not listed in the CISA KEV catalog. Based on the description, it is inferred that the most likely exploitation path involves a local or privileged user performing block operations, such as dd or using blk‑trace utilities, which invoke blk_add_trace from process context with preemption enabled. Triggering the BUG can cause the kernel to panic, resulting in an outage. No remote exploitation or privilege escalation barrier is known from the provided data.