nilfs2: fix potential oob read in nilfs_btree_check_delete()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 17c76b0104e4a6513983777e1a17e0297a12b0c4 · < 257f9e5185eb6de83377caea686c306e22e871f2| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix potential oob read in nilfs_btree_check_delete()
The function nilfs_btree_check_delete(), which checks whether degeneration to direct mapping occurs before deleting a b-tree entry, causes memory access outside the block buffer when retrieving the maximum key if the root node has no entries.
This does not usually happen because b-tree mappings with 0 child nodes are never created by mkfs.nilfs2 or nilfs2 itself. However, it can happen if the b-tree root node read from a device is configured that way, so fix this potential issue by adding a check for that case.
From the CVE record · Linux
The Linux kernel’s nilfs2 code can read outside a block buffer while checking deletion of a b-tree entry. This can occur when a b-tree root node read from a device has no entries; the input does not establish how an attacker could cause that condition or whether authentication or user interaction is required.
Engineers running Linux kernels with nilfs2 should check whether their kernel includes the fix; affected versions are not specified.