Impact
An incorrect initialization order in the Linux ext4 filesystem code causes ext4_percpu_param_init() to run after ext4_mb_init(). When a block bitmap validation fails, the code attempts to update a per‑CPU counter that has not yet been initialized, leading to a panic and a system crash. This compromises availability by providing a denial‑of‑service vector. The flaw maps to uninitialized object usage (CWE-908).
Affected Systems
All Linux kernel builds containing the ext4 filesystem module before the patch that reorders the initialization calls are affected. Since no specific kernel version range is listed, any upstream release older than the fix may be impacted.
Risk and Exploitability
The vulnerability requires that an attacker be able to trigger ext4 block‑bitmap validation, typically by mounting an ext4 filesystem or executing filesystem tests. The likely attack vector is local: an attacker with sufficient privileges to mount or run tests can provoke the crash. No publicly available exploit is known and an EPSS score is not reported. The CVSS score of 5.5 indicates medium severity, and the vulnerability is not yet listed in the CISA KEV catalog.
OpenCVE Enrichment