ext4: don't set up encryption key during jbd2 transaction
In the Linux kernel, the following vulnerability has been resolved: ext4: don't set up encryption key during jbd2 transaction Commit a80f7fcf1867 ("ext4: fixup ext4_fc_track_* functions' signature") extended the scope of the transaction in ext4_unlink() too far, making it include the call to ext4_find_entry(). However, ext4_find_entry() can deadlock when called from within a transaction because it may need to set up the directory's encryption key. Fix this by restoring the transaction to its original scope.
02 / AFFECTED SOFTWARE
Affected packages
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
In the Linux kernel, the following vulnerability has been resolved: ext4: don't set up encryption key during jbd2 transaction Commit a80f7fcf1867 ("ext4: fixup ext4_fc_track_* functions' signature") extended the scope of the transaction in ext4_unlink() too far, making it include the call to ext4_find_entry(). However, ext4_find_entry() can deadlock when called from within a transaction because it may need to set up the directory's encryption key. Fix this by restoring the transaction to its original scope.
05 / REFERENCES
Further evidence
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/1ba993208bcfd691e241483420a2a761d3f15750
- https://git.kernel.org/stable/c/206dd3acfb9bca54a25b228c7c7c2257eedde09b
- https://git.kernel.org/stable/c/23ad034760dd38e12b0e0e1b28b9629f330810a1
- https://git.kernel.org/stable/c/4c0d5778385cb3618ff26a561ce41de2b7d9de70
- https://git.kernel.org/stable/c/6220ec405571ded17efedc56587190b542adf246
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50436.json
- https://nvd.nist.gov/vuln/detail/CVE-2022-50436