# CVE-2023-45896: Information disclosure in n/a

> A physically proximate attacker can read kernel memory by mounting a malicious NTFS filesystem if unprivileged mounts are enabled.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 28 Aug 2024
- **Updated:** 3 Nov 2025
- **Also known as:** BELL-CVE-2023-45896, DEBIAN-CVE-2023-45896, GHSA-9477-m2w2-6wg3, ROOT-OS-UBUNTU-2204-CVE-2023-45896, UBUNTU-CVE-2023-45896

## What is CVE-2023-45896?

CVE-2023-45896 is a high-severity vulnerability in n/a, published on 28 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ntfs3 in the Linux kernel through 6.8.0 allows a physically proximate attacker to read kernel memory by mounting a filesystem (e.g., if a Linux distribution is configured to allow unprivileged mounts of removable media) and then leveraging local access to trigger an out-of-bounds read. A length value can be larger than the amount of memory allocated. NOTE: the supplier's perspective is that there is no vulnerability when an attack requires an attacker-modified filesystem image.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2023-45896?


## How do I fix CVE-2023-45896?

Apply the vendor's patch.

## Is CVE-2023-45896 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-45896 and fix it if it is affected.

What it is: CVE-2023-45896 is a high-severity vulnerability in n/a, published on 28 Aug 2024. 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-2023-45896 in the wild and no public exploit code.

Affected product: n/a. 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-2023-45896/ (Markdown: https://insights.sbomify.com/CVE-2023-45896/index.md)
```

## Sources

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

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