hfsplus: return error when node already exists in hfs_bnode_create
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1ca428769cb4737a25bd32fb4d1573cc09eeaeef, Kernel 2e6ff6a6fc69cc17ed10c9cb6242935d52acd52d, Kernel 2e9185a42e0e237c74435fd092b7c34537c62156 and 5 more.
In the Linux kernel, the following vulnerability has been resolved: hfsplus: return error when node already exists in hfs_bnode_create When hfs_bnode_create() finds that a node is already hashed (which should not happen in normal operation), it currently returns the existing node without incrementing its reference count. This causes a reference count inconsistency that leads to a kernel panic when the node is later freed in hfs_bnode_put(): kernel BUG at fs/hfsplus/bnode.c:676! BUG_ON(!atomic_read(&node->refcnt)) This scenario can occur when hfs_bmap_alloc() attempts to allocate a node that is already in use (e.g., when node 0's bitmap bit is incorrectly unset), or due to filesystem corruption. Returning an existing node from a create path is not normal operation. Fix this by returning ERR_PTR(-EEXIST) instead of the node when it's already hashed. This properly signals the error condition to callers, which already check for IS_ERR() return values.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.16, >=634725a92938b0f282b17cec0b007dca77adebd2 <1ca428769cb4737a25bd32fb4d1573cc09eeaeef, >=634725a92938b0f282b17cec0b007dca77adebd2 <2e6ff6a6fc69cc17ed10c9cb6242935d52acd52d, >=634725a92938b0f282b17cec0b007dca77adebd2 <2e9185a42e0e237c74435fd092b7c34537c62156, >=634725a92938b0f282b17cec0b007dca77adebd2 <507a1de58c21c95ad7c44afccaf1222d1c42246b, >=634725a92938b0f282b17cec0b007dca77adebd2 <51838112d9c22502333c3085ca0c0d691e7093c6, >=634725a92938b0f282b17cec0b007dca77adebd2 <7b57ada854b32310f224abd61bcfec2d5790ff0a, >=634725a92938b0f282b17cec0b007dca77adebd2 <986455135b95f32c1f142068e451098fc751749e, >=634725a92938b0f282b17cec0b007dca77adebd2 <d8a73cc46c8462a969a7516131feb3096f4c49d3 | 1ca428769cb4737a25bd32fb4d1573cc09eeaeef, 2e6ff6a6fc69cc17ed10c9cb6242935d52acd52d, 2e9185a42e0e237c74435fd092b7c34537c62156, 507a1de58c21c95ad7c44afccaf1222d1c42246b, 51838112d9c22502333c3085ca0c0d691e7093c6, 7b57ada854b32310f224abd61bcfec2d5790ff0a, 986455135b95f32c1f142068e451098fc751749e, d8a73cc46c8462a969a7516131feb3096f4c49d3 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket