CVE-2024-47699
Linux Nilfs2 Null Pointer Dereference Vulnerability
Description
In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() Patch series "nilfs2: fix potential issues with empty b-tree nodes". This series addresses three potential issues with empty b-tree nodes that can occur with corrupted filesystem images, including one recently discovered by syzbot. This patch (of 3): If a b-tree is broken on the device, and the b-tree height is greater than 2 (the level of the root node is greater than 1) even if the number of child nodes of the b-tree root is 0, a NULL pointer dereference occurs in nilfs_btree_prepare_insert(), which is called from nilfs_btree_insert(). This is because, when the number of child nodes of the b-tree root is 0, nilfs_btree_do_lookup() does not set the block buffer head in any of path[x].bp_bh, leaving it as the initial value of NULL, but if the level of the b-tree root node is greater than 1, nilfs_btree_get_nonroot_node(), which accesses the buffer memory of path[x].bp_bh, is called. Fix this issue by adding a check to nilfs_btree_root_broken(), which performs sanity checks when reading the root node from the device, to detect this inconsistency. Thanks to Lizhi Xu for trying to solve the bug and clarifying the cause early on.
INFO
Published Date :
Oct. 21, 2024, 12:15 p.m.
Last Modified :
Nov. 8, 2024, 4:15 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
1.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-47699.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-47699 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-47699 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Nov. 08, 2024
Action Type Old Value New Value Added Reference kernel.org https://git.kernel.org/stable/c/2b78e9df10fb7f4e9d3d7a18417dd72fbbc1dfd0 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/1d94dbdfbb64cc48d10dec65cc3c4fbf2497b343 [No types assigned] -
Initial Analysis by [email protected]
Oct. 23, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Changed Reference Type https://git.kernel.org/stable/c/21839b6fbc3c41b3e374ecbdb0cabbbb2c53cf34 No Types Assigned https://git.kernel.org/stable/c/21839b6fbc3c41b3e374ecbdb0cabbbb2c53cf34 Patch Changed Reference Type https://git.kernel.org/stable/c/24bf40740a3da6b4056721da34997ae6938f3da1 No Types Assigned https://git.kernel.org/stable/c/24bf40740a3da6b4056721da34997ae6938f3da1 Patch Changed Reference Type https://git.kernel.org/stable/c/3644554d308ddf2669e459a1551a7edf60b2d62b No Types Assigned https://git.kernel.org/stable/c/3644554d308ddf2669e459a1551a7edf60b2d62b Patch Changed Reference Type https://git.kernel.org/stable/c/73d23ecf234b7a6d47fb883f2dabe10e3230b31d No Types Assigned https://git.kernel.org/stable/c/73d23ecf234b7a6d47fb883f2dabe10e3230b31d Patch Changed Reference Type https://git.kernel.org/stable/c/9403001ad65ae4f4c5de368bdda3a0636b51d51a No Types Assigned https://git.kernel.org/stable/c/9403001ad65ae4f4c5de368bdda3a0636b51d51a Patch Changed Reference Type https://git.kernel.org/stable/c/db73500d3f0e558eb642aae1d4782e7726b4a03f No Types Assigned https://git.kernel.org/stable/c/db73500d3f0e558eb642aae1d4782e7726b4a03f Patch Changed Reference Type https://git.kernel.org/stable/c/f68523e0f26faade18833fbef577a4295d8e2c94 No Types Assigned https://git.kernel.org/stable/c/f68523e0f26faade18833fbef577a4295d8e2c94 Patch Added CWE NIST CWE-476 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 2.6.30 up to (excluding) 5.10.227 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.168 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.113 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.54 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.10.13 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.11 up to (excluding) 6.11.2 -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Oct. 21, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential null-ptr-deref in nilfs_btree_insert() Patch series "nilfs2: fix potential issues with empty b-tree nodes". This series addresses three potential issues with empty b-tree nodes that can occur with corrupted filesystem images, including one recently discovered by syzbot. This patch (of 3): If a b-tree is broken on the device, and the b-tree height is greater than 2 (the level of the root node is greater than 1) even if the number of child nodes of the b-tree root is 0, a NULL pointer dereference occurs in nilfs_btree_prepare_insert(), which is called from nilfs_btree_insert(). This is because, when the number of child nodes of the b-tree root is 0, nilfs_btree_do_lookup() does not set the block buffer head in any of path[x].bp_bh, leaving it as the initial value of NULL, but if the level of the b-tree root node is greater than 1, nilfs_btree_get_nonroot_node(), which accesses the buffer memory of path[x].bp_bh, is called. Fix this issue by adding a check to nilfs_btree_root_broken(), which performs sanity checks when reading the root node from the device, to detect this inconsistency. Thanks to Lizhi Xu for trying to solve the bug and clarifying the cause early on. Added Reference kernel.org https://git.kernel.org/stable/c/24bf40740a3da6b4056721da34997ae6938f3da1 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/73d23ecf234b7a6d47fb883f2dabe10e3230b31d [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/f68523e0f26faade18833fbef577a4295d8e2c94 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/21839b6fbc3c41b3e374ecbdb0cabbbb2c53cf34 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/db73500d3f0e558eb642aae1d4782e7726b4a03f [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/3644554d308ddf2669e459a1551a7edf60b2d62b [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/9403001ad65ae4f4c5de368bdda3a0636b51d51a [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-47699 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-47699
weaknesses.