# CVE-2025-68728: ntfs3: fix uninit memory after failed mi_read in mi_format_new

> A local attacker can trigger uninitialized memory access in the Linux kernel ntfs3 driver, potentially leaking sensitive data or causing a system crash.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-68728, DEBIAN-CVE-2025-68728, GHSA-8mm6-9q78-9fr6, ROOT-OS-DEBIAN-12-CVE-2025-68728, ROOT-OS-DEBIAN-13-CVE-2025-68728, ROOT-OS-UBUNTU-2204-CVE-2025-68728, ROOT-OS-UBUNTU-2404-CVE-2025-68728, UBUNTU-CVE-2025-68728

## What is CVE-2025-68728?

CVE-2025-68728 is a vulnerability in Linux, published on 24 Dec 2025. 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:

ntfs3: fix uninit memory after failed mi_read in mi_format_new

Fix a KMSAN un-init bug found by syzkaller.

ntfs_get_bh() expects a buffer from sb_getblk(), that buffer may not be
uptodate. We do not bring the buffer uptodate before setting it as
uptodate. If the buffer were to not be uptodate, it could mean adding a
buffer with un-init data to the mi record. Attempting to load that record
will trigger KMSAN.

Avoid this by setting the buffer as uptodate, if it’s not already, by
overwriting it.

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


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

Apply the vendor's patch.

## Is CVE-2025-68728 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68728 is a vulnerability in Linux, published on 24 Dec 2025. 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-2025-68728 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-68728/ (Markdown: https://insights.sbomify.com/CVE-2025-68728/index.md)
```

## Sources

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

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