CVE-2026-43066
In the Linux kernel, the following vulnerability has been resolved: …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/0892f12cd49fde5d5db68137923db107f894f3a3
- git.kernel.org/stable/c/19782b4c793b49a6aa4abbb307ddff3610009d21
- git.kernel.org/stable/c/5a63033696e60b5d70816f1d119645ac5b0b0a03
- git.kernel.org/stable/c/9c90449a9ac2cd1ba540ad2561b8b70c1bfb0a25
- git.kernel.org/stable/c/c426231e3d51916e83b6d1ab7ed8a65e83bca5b4
- git.kernel.org/stable/c/ca99cbcc316cdfd2040cc2b13d1426ccb3b3b50b
- git.kernel.org/stable/c/ec0a7500d8eace5b4f305fa0c594dd148f0e8d29
- git.kernel.org/stable/c/f7817ad399d604e8639005d87d148b5ec626ad26
- nvd.nist.gov/vuln/detail/CVE-2026-43066
- cve.org/CVERecord?id=CVE-2026-43066
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.