CVE-2026-43066
Awaiting Analysis Awaiting Analysis - Queue
Memory Leak in Linux Kernel ext4 Filesystem

Publication date: 2026-05-05

Last updated on: 2026-05-05

Assigner: kernel.org

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-05
Last Modified
2026-05-05
Generated
2026-05-07
AI Q&A
2026-05-05
EPSS Evaluated
N/A
NVD
CVE-2026-43066
EUVD
EUVD-2026-27365
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is related to the Linux kernel's ext4 filesystem code, specifically in the function ext4_fc_replay_inode(). During error handling, the function fails to release a resource called iloc.bh properly in several error paths. This resource should be released using brelse(), but some error conditions cause the code to skip this release, leading to a resource leak.

The issue was fixed by adding an additional label in the code to ensure iloc.bh is always released before exiting the function, and by making the function propagate errors correctly instead of always returning success.


How can this vulnerability impact me? :

The vulnerability causes a resource leak in the ext4 filesystem code of the Linux kernel. This could potentially lead to increased memory usage or resource exhaustion over time if the error paths are triggered frequently.

While the description does not specify direct security impacts such as privilege escalation or data corruption, resource leaks can degrade system performance or stability, which might indirectly affect system reliability.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart