# CVE-2025-68767: hfsplus: Verify inode mode when loading from disk

> A local attacker can cause memory corruption or system crash by mounting a maliciously crafted HFS+ filesystem with invalid inode modes.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Jan 2026
- **Updated:** 11 May 2026
- **Also known as:** AZL-74315, BELL-CVE-2025-68767, DEBIAN-CVE-2025-68767, GHSA-mgmc-76vj-qf3j, ROOT-OS-DEBIAN-11-CVE-2025-68767, ROOT-OS-DEBIAN-12-CVE-2025-68767, ROOT-OS-DEBIAN-13-CVE-2025-68767, ROOT-OS-UBUNTU-2204-CVE-2025-68767, ROOT-OS-UBUNTU-2404-CVE-2025-68767, UBUNTU-CVE-2025-68767

## What is CVE-2025-68767?

CVE-2025-68767 is a memory corruption vulnerability in Linux, published on 13 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

hfsplus: Verify inode mode when loading from disk

syzbot is reporting that S_IFMT bits of inode->i_mode can become bogus when
the S_IFMT bits of the 16bits "mode" field loaded from disk are corrupted.

According to [1], the permissions field was treated as reserved in Mac OS
8 and 9. According to [2], the reserved field was explicitly initialized
with 0, and that field must remain 0 as long as reserved. Therefore, when
the "mode" field is not 0 (i.e. no longer reserved), the file must be
S_IFDIR if dir == 1, and the file must be one of S_IFREG/S_IFLNK/S_IFCHR/
S_IFBLK/S_IFIFO/S_IFSOCK if dir == 0.

## Which versions are affected by CVE-2025-68767?


## How do I fix CVE-2025-68767?

Apply the vendor's patch.

## Is CVE-2025-68767 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68767 and fix it if it is affected.

What it is: CVE-2025-68767 is a memory corruption vulnerability in Linux, published on 13 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-68767 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-2025-68767/ (Markdown: https://insights.sbomify.com/CVE-2025-68767/index.md)
```

## Sources

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

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