hfsplus: return error when node already exists in hfs_bnode_create
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 634725a92938b0f282b17cec0b007dca77adebd2 · < 2e6ff6a6fc69cc17ed10c9cb6242935d52acd52d| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's hfsplus code can panic if hfs_bnode_create() encounters a node that is already hashed and returns it without incrementing its reference count. This can occur when allocation targets a node already in use or the filesystem is corrupt. The input does not establish an attacker path, authentication requirement, or user-interaction requirement.
Engineers running Linux kernels with hfsplus support should check their versions; affected versions are not specified.