All reports
Low

kernel: ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-43066

Probability of exploitation in the next 30 days: 0.12%

FIRST EPSS · 2026-11-18

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths During code review, Joseph found that ext4_fc_replay_inode() calls ext4_get_fc_inode_loc() 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:

  • ext4_handle_dirty_metadata() failure

  • sync_dirty_buffer() failure

  • ext4_mark_inode_used() failure

  • ext4_iget() failure Fix this by introducing an 'out_brelse' label placed just before the existing 'out' label to ensure iloc.bh is always released. Additionally, make ext4_fc_replay_inode() propagate errors properly instead of always returning 0.

A flaw was found in the Linux kernel's ext4 filesystem. Specific error handling paths within the ext4_fc_replay_inode() function failed to release a buffer head resource, leading to a resource leak. A local attacker could potentially exploit this vulnerability by triggering these error paths, which may result in a Denial of Service (DoS) due to resource exhaustion.