ext4: don't set up encryption key during jbd2 transaction
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's ext4_unlink() can call ext4_find_entry() while a jbd2 transaction is active. If that call needs to set up a directory encryption key, it can deadlock. The input does not specify an attacker path, authentication requirements, or user interaction.
Engineers running Linux kernels containing the affected ext4 transaction-scope change should check their versions; no affected version range is provided.