ext4: do not create EA inode under buffer lock
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ext4: do not create EA inode under buffer lock
ext4_xattr_set_entry() creates new EA inodes while holding buffer lock on the external xattr block. This is problematic as it nests all the allocation locking (which acquires locks on other buffers) under the buffer lock. This can even deadlock when the filesystem is corrupted and e.g. quota file is setup to contain xattr block as data block. Move the allocation of EA inode out of ext4_xattr_set_entry() into the callers.
From the CVE record · Linux
The Linux kernel's ext4 code can create an extended-attribute inode while holding a buffer lock. If the filesystem is corrupted, nested allocation locks can cause a deadlock. The input does not establish whether an attacker can trigger this or what access would be required.
Engineers running the Linux kernel with ext4 should check their versions; affected versions are not specified.