During ocfs2 write operations the Linux kernel’s journaling subsystem may attempt to acquire more transaction credits than the maximum allowed, triggering warnings such as "kworker wants too many credits" and potentially causing kernel panics or data corruption. The described patch splits large extents into smaller batches and defers orphan inode removal until extent updates finish, preventing over‑crediting and removal of stale blocks beyond the end‑of‑file. The result is a high‑impact vulnerability that can lead to service disruption and loss of data integrity if an attacker or misconfiguring workload forces excessive journal activity.

All Linux kernel releases that include the ocfs2 filesystem before the official patch. The affected code paths are in ocfs2_dio_end_io_write, ocfs2_change_extent_flag, ocfs2_split_extent, and related journaling functions. No specific kernel version range is listed, but any kernel bundled with ocfs2 is potentially vulnerable until the fix is applied.

The CVSS score is not disclosed and the EPSS score is unavailable, so the quantitative risk is unknown. It is inferred that exploitation requires local or elevated privileges that allow heavy ocfs2 I/O to trigger the credit exhaustion logic. The vulnerability is not currently listed in the CISA KEV catalog, suggesting no widespread known exploitation yet. Nevertheless, the failure mode could produce a denial of service or data corruption, making it a high priority for mitigation. Based on the description, the likely attack vector is through sustained ocfs2 read/write workloads that provoke journal overcommitment.