ext4: don't set up encryption key during jbd2 transaction
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1ba993208bcfd691e241483420a2a761d3f15750, Kernel 206dd3acfb9bca54a25b228c7c7c2257eedde09b, Kernel 23ad034760dd38e12b0e0e1b28b9629f330810a1 and 2 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.10, >=a80f7fcf18672ae4971a6b713b58c0d389aa99fe <1ba993208bcfd691e241483420a2a761d3f15750, >=a80f7fcf18672ae4971a6b713b58c0d389aa99fe <206dd3acfb9bca54a25b228c7c7c2257eedde09b, >=a80f7fcf18672ae4971a6b713b58c0d389aa99fe <23ad034760dd38e12b0e0e1b28b9629f330810a1, >=a80f7fcf18672ae4971a6b713b58c0d389aa99fe <4c0d5778385cb3618ff26a561ce41de2b7d9de70, >=a80f7fcf18672ae4971a6b713b58c0d389aa99fe <6220ec405571ded17efedc56587190b542adf246 | 1ba993208bcfd691e241483420a2a761d3f15750, 206dd3acfb9bca54a25b228c7c7c2257eedde09b, 23ad034760dd38e12b0e0e1b28b9629f330810a1, 4c0d5778385cb3618ff26a561ce41de2b7d9de70, 6220ec405571ded17efedc56587190b542adf246 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket