https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 23:48:24 +0000 https://vulnerability.circl.lu/vuln/cve-2026-43066 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths</p> <p>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().</p> <p>However, several error paths jump to the &#39;out&#39; label without releasing iloc.bh:</p> <p>- ext4_handle_dirty_metadata() failure - sync_dirty_buffer() failure - ext4_mark_inode_used() failure - ext4_iget() failure</p> <p>Fix this by introducing an &#39;out_brelse&#39; label placed just before the existing &#39;out&#39; label to ensure iloc.bh is always released.</p> <p>Additionally, make ext4_fc_replay_inode() propagate errors properly instead of always returning 0.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths</p> <p>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().</p> <p>However, several error paths jump to the &#39;out&#39; label without releasing iloc.bh:</p> <p>- ext4_handle_dirty_metadata() failure - sync_dirty_buffer() failure - ext4_mark_inode_used() failure - ext4_iget() failure</p> <p>Fix this by introducing an &#39;out_brelse&#39; label placed just before the existing &#39;out&#39; label to ensure iloc.bh is always released.</p> <p>Additionally, make ext4_fc_replay_inode() propagate errors properly instead of always returning 0.</p> https://vulnerability.circl.lu/vuln/cve-2026-43066