# CVE-2026-93095: hfsplus: validate thread record before delete key rebuild

> A memory corruption vulnerability in the Linux kernel's HFS+ filesystem allows attackers to execute code or cause denial of service via a corrupted image.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102660, BELL-CVE-2026-93095, DEBIAN-CVE-2026-93095, GHSA-g2xv-9xm6-cmw4, UBUNTU-CVE-2026-93095

## What is CVE-2026-93095?

CVE-2026-93095 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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().

## Which versions are affected by CVE-2026-93095?


## How do I fix CVE-2026-93095?

Apply the vendor's patch.

## Is CVE-2026-93095 being exploited?

There is no known exploitation of CVE-2026-93095 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93095 and fix it if it is affected.

What it is: CVE-2026-93095 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93095 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93095/ (Markdown: https://insights.sbomify.com/CVE-2026-93095/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93095
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93095
- OSV: https://osv.dev/vulnerability/CVE-2026-93095

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93095/
Summaries are generated and may contain mistakes; the official description above is the record.