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
5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 builds before 0892f12cd49fde5d5db68137923db107f894f3a3; 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 builds before 5a63033696e60b5d70816f1d119645ac5b0b0a03; 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 builds before 9c90449a9ac2cd1ba540ad2561b8b70c1bfb0a25; from 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 before ca99cbcc316cdfd2040cc2b13d1426ccb3b3b50b; from 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 before 19782b4c793b49a6aa4abbb307ddff3610009d21; from 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 before f7817ad399d604e8639005d87d148b5ec626ad26; from 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 before c426231e3d51916e83b6d1ab7ed8a65e83bca5b4; from 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 before ec0a7500d8eace5b4f305fa0c594dd148f0e8d29
from 5.10 before 5.10.253; from 5.11 before 5.15.203; from 5.16 before 6.1.168; from 6.2 before 6.6.131; from 6.7 before 6.12.80; from 6.13 before 6.18.21; from 6.19 before 6.19.11; 7.0; and 4 more ranges
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.
Printed from infosecsignals.com. Every record links back to the agency that published it.
Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.