CVE-2026-45935 json
fs/ntfs3: Fix slab-out-of-bounds read in DeleteIndexEntryRoot
published 5mo ago modified 3mo ago also EUVD-2026-32219
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 4%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.15.202, 6.1.165, 6.6.128, 6.12.75, 6.18.14, 6.19.4, 7.0
- linux Debian 12 6.1.170-1
- linux Debian 13 6.12.85-1
- linux Debian 14 6.18.14-1
debian advisories DEBIAN-CVE-2026-45935
- linux Ubuntu 22.04 LTS 5.15.0-186.196
- linux Ubuntu 24.04 LTS 6.8.0-134.134
- linux-aws Ubuntu 22.04 LTS 5.15.0-1112.119
- linux-aws Ubuntu 24.04 LTS 6.8.0-1060.63
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1112.122
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1063.69
- linux-gke Ubuntu 22.04 LTS 5.15.0-1108.114
- linux-gke Ubuntu 24.04 LTS 6.8.0-1058.64
ubuntu advisories UBUNTU-CVE-2026-45935
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/36c03f7f177b34d51f1cf1d2304b1074607bf4b0 commit
- git.kernel.org/stable/c/b271c9cb85927210b1b799e55ee7f702d12b4336 commit
- git.kernel.org/stable/c/a584b9d1059b29e97e17c919274e9adfb846f2a0 commit
- git.kernel.org/stable/c/c065541b71b79874c83d418a9acd18ad5826339b commit
- git.kernel.org/stable/c/78942172d5bff4d4afed8674abc09cc560ce44a0 commit
- git.kernel.org/stable/c/f3b437a4c3e022a1449658ae9f3dd34859894513 commit
- git.kernel.org/stable/c/b2bc7c44ed1779fc9eaab9a186db0f0d01439622 commit
Is CVE-2026-45935 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-45935 updated
kernel: fs/ntfs3: Fix slab-out-of-bounds read in DeleteIndexEntryRoot
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
- Technology feeds
References
-
git.kernel.org
/stable/c/36c03f7f177b34d51f1cf1d2304b1074607bf4b0
patch
-
git.kernel.org
/stable/c/b271c9cb85927210b1b799e55ee7f702d12b4336
patch
-
git.kernel.org
/stable/c/a584b9d1059b29e97e17c919274e9adfb846f2a0
patch
-
git.kernel.org
/stable/c/c065541b71b79874c83d418a9acd18ad5826339b
patch
-
git.kernel.org
/stable/c/78942172d5bff4d4afed8674abc09cc560ce44a0
patch
-
git.kernel.org
/stable/c/f3b437a4c3e022a1449658ae9f3dd34859894513
patch
-
git.kernel.org
/stable/c/b2bc7c44ed1779fc9eaab9a186db0f0d01439622
patch
Sources
- CVE List CVE-2026-45935
- NVD CVE-2026-45935
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.