In the Linux kernel, the following vulnerability has been resolved: hfsplus: fix missing hfs_bnode_get() in __hfs_bnode_create When sync() and… (CVE-2025-68774)
A concurrency vulnerability in the Linux kernel's HFS+ filesystem code was fixed by ensuring proper reference counting of bnodes during concurrent sync() and link() operations. The issue involved missing calls to hfs_bnode_get() when reusing a newly created bnode, causing incorrect reference counts and potential kernel BUGs. This flaw could lead to kernel crashes due to improper handling of bnode reference counts in multi-threaded scenarios.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's HFS+ filesystem arises when sync() and link() operations run concurrently, causing two threads to simultaneously attempt to create the same bnode. Thread A creates and inserts the bnode with a reference count of 1, while Thread B detects the bnode already exists and reuses it without incrementing the reference count. This results in both threads having a refcnt of 1, leading to a BUG_ON condition when the node is later released. The fix involves calling hfs_bnode_get() when reusing a bnode created by another thread to correctly increment the reference count and prevent kernel crashes. This bug was previously fixed in the HFS filesystem but remained in HFS+ until now.
Potential Impact
The vulnerability can cause kernel crashes (denial of service) due to incorrect reference counting of bnodes in the HFS+ filesystem when concurrent operations occur. There is no indication of confidentiality or integrity impact. The severity is high due to the potential for system instability or denial of service.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to call hfs_bnode_get() when reusing a bnode created by another thread, ensuring correct reference counting. Users should apply the official kernel update that includes this fix once available. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: hfsplus: fix missing hfs_bnode_get() in __hfs_bnode_create When sync() and… (CVE-2025-68774)
Description
A concurrency vulnerability in the Linux kernel's HFS+ filesystem code was fixed by ensuring proper reference counting of bnodes during concurrent sync() and link() operations. The issue involved missing calls to hfs_bnode_get() when reusing a newly created bnode, causing incorrect reference counts and potential kernel BUGs. This flaw could lead to kernel crashes due to improper handling of bnode reference counts in multi-threaded scenarios.
CVSS v3.1
Score 7.5high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's HFS+ filesystem arises when sync() and link() operations run concurrently, causing two threads to simultaneously attempt to create the same bnode. Thread A creates and inserts the bnode with a reference count of 1, while Thread B detects the bnode already exists and reuses it without incrementing the reference count. This results in both threads having a refcnt of 1, leading to a BUG_ON condition when the node is later released. The fix involves calling hfs_bnode_get() when reusing a bnode created by another thread to correctly increment the reference count and prevent kernel crashes. This bug was previously fixed in the HFS filesystem but remained in HFS+ until now.
Potential Impact
The vulnerability can cause kernel crashes (denial of service) due to incorrect reference counting of bnodes in the HFS+ filesystem when concurrent operations occur. There is no indication of confidentiality or integrity impact. The severity is high due to the potential for system instability or denial of service.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to call hfs_bnode_get() when reusing a bnode created by another thread, ensuring correct reference counting. Users should apply the official kernel update that includes this fix once available. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-2wrv-52xx-6xxv
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-68774"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6b72d29c2644c7f84776ac
Added to database: 07/30/2026, 15:50:42 UTC
Last enriched: 07/30/2026, 18:57:47 UTC
Last updated: 09/10/2026, 19:38:47 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.