Linux kernel
cpe:2.3:a:linux:linux_kernel:*:*:*:*:*:*:*, +4 more
A vulnerability in the Linux kernel's HFS+ file system implementation can cause a kernel panic. The issue arises in the 'hfs_bnode_create' function, where the code improperly handles nodes that are already hashed. Instead of incrementing the reference count of the existing node, it returns the node as is, creating a reference count inconsistency. This flaw can lead to a kernel panic when the node is eventually freed, as the reference count does not accurately reflect its usage. This problem can occur due to filesystem corruption or when the bitmap management of node allocations is flawed.
Exploiting this vulnerability causes a kernel panic, disrupting system operations and potentially leading to a denial of service.
To reproduce this vulnerability, create a scenario where the HFS+ file system is corrupted or where the bitmap management incorrectly indicates that a node is available when it is not. This can be done by manipulating the file system's metadata or by using a tool that simulates such conditions. Once the file system is in this state, the 'hfs_bnode_create' function will return a node that is already hashed without the proper reference count, leading to a kernel panic when the node is freed.
Users can upgrade to the latest stable version of the Linux kernel, where this vulnerability has been addressed. Instructions for upgrading the kernel can be found in the official Linux documentation.
Our algorithm analyzes dozens of metrics to generate these 8 key vulnerability categories, which are then combined to calculate the overall risk score.