CVE-2026-43066: ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths
In the Linux kernel, the following vulnerability has been resolved:
ext4: fix iloc.bh leak in ext4fcreplayinode() error paths
During code review, Joseph found that ext4fcreplayinode() calls ext4getfcinodeloc() to get the inode location, which holds a reference to iloc.bh that must be released via brelse().
However, several error paths jump to the 'out' label without releasing iloc.bh:
- ext4handledirtymetadata() failure - syncdirtybuffer() failure - ext4markinodeused() failure - ext4iget() failure
Fix this by introducing an 'outbrelse' label placed just before the existing 'out' label to ensure iloc.bh is always released.
Additionally, make ext4fcreplayinode() propagate errors properly instead of always returning 0.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43066?
CVE-2026-43066 has been classified as a medium-severity vulnerability.
How do I fix CVE-2026-43066?
To fix CVE-2026-43066, update to the latest Linux kernel version where this vulnerability has been patched.
What is the impact of CVE-2026-43066 on ext4 file systems?
The impact of CVE-2026-43066 could potentially lead to memory leaks affecting system performance.
Which versions of the Linux kernel are affected by CVE-2026-43066?
CVE-2026-43066 affects certain versions of the Linux kernel that use the ext4 file system.
Can CVE-2026-43066 be exploited remotely?
CVE-2026-43066 is not considered to be a remotely exploitable vulnerability.