# CVE-2026-45935: fs/ntfs3: Fix slab-out-of-bounds read in DeleteIndexEntryRoot

> A slab-out-of-bounds read in the Linux kernel NTFS3 driver allows attackers to trigger heap buffer overflows via maliciously crafted NTFS images, potentially leading to code execution or system crashes.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 27 May 2026
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2026-45935, DEBIAN-CVE-2026-45935, GHSA-4cvx-h6xx-mj53, ROOT-OS-UBUNTU-2204-CVE-2026-45935, ROOT-OS-UBUNTU-2404-CVE-2026-45935, UBUNTU-CVE-2026-45935

## What is CVE-2026-45935?

CVE-2026-45935 is a high-severity memory corruption vulnerability in Linux kernel, published on 27 May 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:

fs/ntfs3: Fix slab-out-of-bounds read in DeleteIndexEntryRoot

In the 'DeleteIndexEntryRoot' case of the 'do_action' function, the
entry size ('esize') is retrieved from the log record without adequate
bounds checking.

Specifically, the code calculates the end of the entry ('e2') using:
    e2 = Add2Ptr(e1, esize);

It then calculates the size for memmove using 'PtrOffset(e2, ...)',
which subtracts the end pointer from the buffer limit. If 'esize' is
maliciously large, 'e2' exceeds the used buffer size. This results in
a negative offset which, when cast to size_t for memmove, interprets
as a massive unsigned integer, leading to a heap buffer overflow.

This commit adds a check to ensure that the entry size ('esize') strictly
fits within the remaining used space of the index header before performing
memory operations.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-45935 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45935 is a high-severity memory corruption vulnerability in Linux kernel, published on 27 May 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-2026-45935 in the wild and no public exploit code.

Affected product: Linux kernel. 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-45935/ (Markdown: https://insights.sbomify.com/CVE-2026-45935/index.md)
```

## Sources

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

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