CVE-2024-47757: nilfs2: fix potential oob read in nilfs_btree_check_delete()
First published: Mon Oct 21 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | >=2.6.30<5.10.227 | |
| Linux Kernel | >=5.11<5.15.168 | |
| Linux Kernel | >=5.16<6.1.113 | |
| Linux Kernel | >=6.2<6.6.54 | |
| Linux Kernel | >=6.7<6.10.13 | |
| Linux Kernel | >=6.11<6.11.2 | |
| debian/linux | <=5.10.223-1 | 5.10.234-1 6.1.129-1 6.1.128-1 6.12.20-1 6.12.21-1 |
| debian/linux-6.1 | 6.1.129-1~deb11u1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/257f9e5185eb6de83377caea686c306e22e871f2
- https://git.kernel.org/stable/c/a33e967b681e088a125b979975c93e3453e686cd
- https://git.kernel.org/stable/c/a8abfda768b9f33630cfbc4af6c4214f1e5681b0
- https://git.kernel.org/stable/c/c4cbcc64bb31e67e02940ce060cc77f7180564cf
- https://git.kernel.org/stable/c/c4f8554996e8ada3be872dfb8f60e93bcf15fb27
- https://git.kernel.org/stable/c/d20674f31626e0596ae4c1d9401dfb6739b81b58
- https://git.kernel.org/stable/c/ed76d381dae125b81d09934e365391a656249da8
- https://git.kernel.org/stable/c/f3a9859767c7aea758976f5523903d247e585129
- https://git.kernel.org/stable/c/f9c96351aa6718b42a9f42eaf7adce0356bdb5e8
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47757
- https://nvd.nist.gov/vuln/detail/CVE-2024-47757
- https://launchpad.net/bugs/cve/CVE-2024-47757
- https://security-tracker.debian.org/tracker/CVE-2024-47757
- https://ubuntu.com/security/CVE-2024-47757
- https://git.kernel.org/linus/f9c96351aa6718b42a9f42eaf7adce0356bdb5e8
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.
- agent/title
- agent/type
- agent/first-publish-date
- agent/weakness
- agent/remedy
- agent/severity
- agent/author
- agent/references
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/trending
- collector/launchpad-cve
- source/Launchpad
- agent/source
- agent/tags
- collector/usn-cve
- source/Ubuntu
- agent/description
- agent/event
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-cve
- agent/softwarecombine
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/linux kernel
- version/linux kernel/2.6.30
- version/linux kernel/5.11
- version/linux kernel/5.16
- version/linux kernel/6.2
- version/linux kernel/6.7
- version/linux kernel/6.11
- package-manager/debian