CVE-2026-45960: hfsplus: return error when node already exists in hfs_bnode_create
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1ca428769cb4737a25bd32fb4d1573cc09eeaeef, 2e6ff6a6fc69cc17ed10c9cb6242935d52acd52d, 2e9185a42e0e237c74435fd092b7c34537c62156.
Low priority for now. Upgrade to Linux Linux 1ca428769cb4737a25bd32fb4d1573cc09eeaeef, 2e6ff6a6fc69cc17ed10c9cb6242935d52acd52d, 2e9185a42e0e237c74435fd092b7c34537c62156 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 27, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel2.6.16.1 and later · before 5.10.252
- linux linux kernel5.11 and later · before 5.15.202
- linux linux kernel5.16 and later · before 6.1.165
- linux linux kernel6.2 and later · before 6.6.128
- linux linux kernel6.7 and later · before 6.12.75
- linux linux kernel6.13 and later · before 6.18.14
- linux linux kernel6.19 and later · before 6.19.4
- linux linux kernel2.6.16
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.16affected
- 634725a92938b0f282b17cec0b007dca77adebd2 and later · before 1ca428769cb4737a25bd32fb4d1573cc09eeaeefaffected · git
- 634725a92938b0f282b17cec0b007dca77adebd2 and later · before 507a1de58c21c95ad7c44afccaf1222d1c42246baffected · git
- 634725a92938b0f282b17cec0b007dca77adebd2 and later · before 986455135b95f32c1f142068e451098fc751749eaffected · git
- 634725a92938b0f282b17cec0b007dca77adebd2 and later · before 7b57ada854b32310f224abd61bcfec2d5790ff0aaffected · git
- 634725a92938b0f282b17cec0b007dca77adebd2 and later · before 51838112d9c22502333c3085ca0c0d691e7093c6affected · git
- 634725a92938b0f282b17cec0b007dca77adebd2 and later · before 2e6ff6a6fc69cc17ed10c9cb6242935d52acd52daffected · git
- 634725a92938b0f282b17cec0b007dca77adebd2 and later · before 2e9185a42e0e237c74435fd092b7c34537c62156affected · git
- 634725a92938b0f282b17cec0b007dca77adebd2 and later · before d8a73cc46c8462a969a7516131feb3096f4c49d3affected · git
- before 2.6.16not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.170-1 | 6.1.170-1 |
| Debian:13 | linux | before 6.12.85-1 | 6.12.85-1 |
| Debian:14 | linux | before 6.18.14-1 | 6.18.14-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-45954May 27, 2026 · fbdev: au1200fb: Fix a memory leak in au1200fb_drv_probe()22Monitor
- ← EarlierCVE-2026-45958May 27, 2026 · drm/exynos: vidi: fix to avoid directly dereferencing user pointer28Monitor
- Later →CVE-2026-45962May 27, 2026 · ublk: Validate SQE128 flag before accessing the cmd22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1ca428769cb4737a25bd32fb4d1573cc09eeaeef | Vendor (CNA) |
| Linux Linux | 2e6ff6a6fc69cc17ed10c9cb6242935d52acd52d | Vendor (CNA) |
| Linux Linux | 2e9185a42e0e237c74435fd092b7c34537c62156 | Vendor (CNA) |
| Linux Linux | 507a1de58c21c95ad7c44afccaf1222d1c42246b | Vendor (CNA) |
| Linux Linux | 51838112d9c22502333c3085ca0c0d691e7093c6 | Vendor (CNA) |
| Linux Linux | 7b57ada854b32310f224abd61bcfec2d5790ff0a | Vendor (CNA) |
| Linux Linux | 986455135b95f32c1f142068e451098fc751749e | Vendor (CNA) |
| Linux Linux | d8a73cc46c8462a969a7516131feb3096f4c49d3 | Vendor (CNA) |
| debian:linux | 6.1.170-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2e6ff6a6fc69cc17ed10c9cb6242935d52acd52d
- git.kernel.org/stable/c/2e9185a42e0e237c74435fd092b7c34537c62156
- git.kernel.org/stable/c/507a1de58c21c95ad7c44afccaf1222d1c42246b
- git.kernel.org/stable/c/51838112d9c22502333c3085ca0c0d691e7093c6
- git.kernel.org/stable/c/7b57ada854b32310f224abd61bcfec2d5790ff0a
- git.kernel.org/stable/c/986455135b95f32c1f142068e451098fc751749e
- git.kernel.org/stable/c/d8a73cc46c8462a969a7516131feb3096f4c49d3
Vendor advisories and official records. Exploit/PoC links are deliberately left out.