nilfs2: fix infinite loop in nilfs_mdt_get_block()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ bdb265eae08db578e7cf5739be16f389d495fc75 · < 25457d07c8146e57d28906c663def033dc425af6| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix infinite loop in nilfs_mdt_get_block()
If the disk image that nilfs2 mounts is corrupted and a virtual block address obtained by block lookup for a metadata file is invalid, nilfs_bmap_lookup_at_level() may return the same internal return code as -ENOENT, meaning the block does not exist in the metadata file.
This duplication of return codes confuses nilfs_mdt_get_block(), causing it to read and create a metadata block indefinitely.
In particular, if this happens to the inode metadata file, ifile, semaphore i_rwsem can be left held, causing task hangs in lock_mount.
Fix this issue by making nilfs_bmap_lookup_at_level() treat virtual block address translation failures with -ENOENT as metadata corruption instead of returning the error code.
From the CVE record · Linux
The Linux kernel’s nilfs2 metadata block lookup can loop indefinitely when a mounted disk image is corrupted and a metadata block address is invalid. This can leave a semaphore held and cause tasks to hang during mounting. The input does not specify an attacker access or authentication requirement.
Administrators running the Linux kernel with nilfs2 support should check their systems; affected versions are not specified.