ext4: avoid use-after-free in ext4_ext_show_leaf()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.227, 5.15.168, 6.1.113, 6.6.55, 6.10.14, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: ext4: avoid use-after-free in ext4_ext_show_leaf() In ext4_find_extent(), path may be freed by error or be reallocated, so using a previously saved *ppath may have been freed and thus may trigger use-after-free, as follows: ext4_split_extent path = *ppath; ext4_split_extent_at(ppath) path = ext4_find_extent(ppath) ext4_split_extent_at(ppath) // ext4_find_extent fails to free path // but zeroout succeeds ext4_ext_show_leaf(inode, path) eh = path[depth].p_hdr // path use-after-free !!! Similar to ext4_split_extent_at(), we use *ppath directly as an input to ext4_ext_show_leaf(). Fix a spelling error by the way. Same problem in ext4_ext_handle_unwritten_extents(). Since 'path' is only used in ext4_ext_show_leaf(), remove 'path' and use *ppath directly. This issue is triggered only when EXT_DEBUG is defined and therefore does not affect functionality.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From dfe5080939ea4686b3414b5d970a9b26733c57a4 · fixed in b0cb4561fc4284d04e69c8a66c8504928ab2484e; From dfe5080939ea4686b3414b5d970a9b26733c57a4 · fixed in 4999fed877bb64e3e7f9ab9996de2ca983c41928; From dfe5080939ea4686b3414b5d970a9b26733c57a4 · fixed in 2eba3b0cc5b8de624918d21f32b5b8db59a90b39; From dfe5080939ea4686b3414b5d970a9b26733c57a4 · fixed in 34b2096380ba475771971a778a478661a791aa15; From dfe5080939ea4686b3414b5d970a9b26733c57a4 · fixed in 8b114f2cc7dd5d36729d040b68432fbd0f0a8868; From dfe5080939ea4686b3414b5d970a9b26733c57a4 · fixed in d483c7cc1796bd6a80e7b3a8fd494996260f6b67; From dfe5080939ea4686b3414b5d970a9b26733c57a4 · fixed in 4e2524ba2ca5f54bdbb9e5153bea00421ef653f5
- Linux Linux
3.18
- KernelLinux
From 3.18.0 · fixed in 5.10.227; From 5.11.0 · fixed in 5.15.168; From 5.16.0 · fixed in 6.1.113; From 6.2.0 · fixed in 6.6.55; From 6.7.0 · fixed in 6.10.14; From 6.11.0 · fixed in 6.11.3
References 7
git.kernel.org
- stable/c/b0cb4561fc4284d04e69c8a66c8504928ab2484e
- stable/c/4999fed877bb64e3e7f9ab9996de2ca983c41928
- stable/c/2eba3b0cc5b8de624918d21f32b5b8db59a90b39
- stable/c/34b2096380ba475771971a778a478661a791aa15
- stable/c/8b114f2cc7dd5d36729d040b68432fbd0f0a8868
- stable/c/d483c7cc1796bd6a80e7b3a8fd494996260f6b67
- stable/c/4e2524ba2ca5f54bdbb9e5153bea00421ef653f5