PT-2026-43827 · Linux · Linux
Published
2026-05-27
·
Updated
2026-05-27
·
CVE-2026-45960
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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.
Found an issue in the description? Have something to add? Feel free to write us 👾
Related Identifiers
Affected Products
Linux