CVE-2024-47757: nilfs2: fix potential oob read in nilfs_btree_check_delete()
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: fix potential oob read in nilfsbtreecheckdelete()
The function nilfsbtreecheckdelete(), 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.
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-47757?
CVE-2024-47757 has a high severity due to its potential to cause out-of-bounds memory access issues.
How do I fix CVE-2024-47757?
To fix CVE-2024-47757, you should upgrade to the latest version of the Linux kernel that has addressed the vulnerability.
Which versions of the Linux kernel are affected by CVE-2024-47757?
CVE-2024-47757 affects Linux kernel versions between 2.6.30 and 5.10.227, as well as versions of specific ranges up to 6.11.2.
What components are involved in CVE-2024-47757?
CVE-2024-47757 specifically involves the nilfs2 filesystem and the function nilfs_btree_check_delete() in the Linux kernel.
Is there a risk of data loss due to CVE-2024-47757?
Yes, due to potential memory access issues, CVE-2024-47757 could lead to data corruption or loss if exploited.