hfsplus: validate thread record before delete key rebuild
Noroxi assessment
Priority: Monitor (action score 31/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.17% (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 33cda0036bc683fc888c20b04a5fc030e3e8413b, 473ea7aa35615829f0de7a71e8691d69dc24e328, 7898beee166c1145c0bca364d687b8437435bf1a.
Low priority for now. Upgrade to Linux Linux 33cda0036bc683fc888c20b04a5fc030e3e8413b, 473ea7aa35615829f0de7a71e8691d69dc24e328, 7898beee166c1145c0bca364d687b8437435bf1a 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: validate thread record before delete key rebuild hfsplus_delete_cat() is called with str == NULL when the last open reference to an unlinked HFS+ hardlink backing inode is closed. In that case, the function finds the catalog thread by CNID and rebuilds the catalog key from thread.nodeName. That reconstruction path reads thread.nodeName.length directly from the catalog B-tree into fd.search_key and then copies length * 2 bytes into fd.search_key->cat.name.unicode. It does not first check that the found record is a thread record or that its size matches the thread name. A corrupted image can therefore provide an oversized thread name length and make hfs_bnode_read() write past the catalog search-key allocation. Read the CNID record through hfsplus_brec_read_cat(), which bounds the record read to sizeof(hfsplus_cat_entry) and verifies that a thread record's size exactly matches nodeName.length. Together, these checks ensure an accepted thread name fits HFSPLUS_MAX_STRLEN. Reject non-thread records before building the delete key from the validated thread name. Share the thread-record-type helper between hfsplus_find_cat() and hfsplus_delete_cat().
- Published
- Sep 17, 2026
- Updated
- Sep 18, 2026
- EPSS
- 0.2% · 7th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
—
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.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 33cda0036bc683fc888c20b04a5fc030e3e8413baffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b9729c51a8b67f8b20b8a8cf395da4be63a0c15baffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before af48abc1b00d865c3f4c4d76b901c44115cb7162affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before e20f3b749ad241df77ec1c3e13a9c22209aa1eb3affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 7898beee166c1145c0bca364d687b8437435bf1aaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before e31985c67ba00a59d9b1340af473c1dbe6c87856affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 473ea7aa35615829f0de7a71e8691d69dc24e328affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before e2ea5cac61acfc11dad22f1d2d4bc71d56c52a20affected · git
- before 2.6.12not 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 | all versions | — |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 33cda0036bc683fc888c20b04a5fc030e3e8413b | Vendor (CNA) |
| Linux Linux | 473ea7aa35615829f0de7a71e8691d69dc24e328 | Vendor (CNA) |
| Linux Linux | 7898beee166c1145c0bca364d687b8437435bf1a | Vendor (CNA) |
| Linux Linux | af48abc1b00d865c3f4c4d76b901c44115cb7162 | Vendor (CNA) |
| Linux Linux | b9729c51a8b67f8b20b8a8cf395da4be63a0c15b | Vendor (CNA) |
| Linux Linux | e20f3b749ad241df77ec1c3e13a9c22209aa1eb3 | Vendor (CNA) |
| Linux Linux | e2ea5cac61acfc11dad22f1d2d4bc71d56c52a20 | Vendor (CNA) |
| Linux Linux | e31985c67ba00a59d9b1340af473c1dbe6c87856 | Vendor (CNA) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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/473ea7aa35615829f0de7a71e8691d69dc24e328
- git.kernel.org/stable/c/7898beee166c1145c0bca364d687b8437435bf1a
- git.kernel.org/stable/c/af48abc1b00d865c3f4c4d76b901c44115cb7162
- git.kernel.org/stable/c/b9729c51a8b67f8b20b8a8cf395da4be63a0c15b
- git.kernel.org/stable/c/e20f3b749ad241df77ec1c3e13a9c22209aa1eb3
- git.kernel.org/stable/c/e2ea5cac61acfc11dad22f1d2d4bc71d56c52a20
- git.kernel.org/stable/c/e31985c67ba00a59d9b1340af473c1dbe6c87856
Vendor advisories and official records. Exploit/PoC links are deliberately left out.