CVE-2026-46072 json
ntfs3: add buffer boundary checks to run_unpack()
published 5mo ago modified 4mo ago also EUVD-2026-32454
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
ntfs3: add buffer boundary checks to run_unpack()
run_unpack() checks `run_buf < run_last` at the top of the while loop but then reads size_size and offset_size bytes via run_unpack_s64() without verifying they fit within the remaining buffer. A crafted NTFS image with truncated run data in an MFT attribute triggers an OOB heap read of up to 15 bytes when the filesystem is mounted.
Add boundary checks before each run_unpack_s64() call to ensure the declared field size does not exceed the remaining buffer.
Found by fuzzing with a source-patched harness (LibAFL + QEMU).
Patch / fix
- Linux Linux 5.15.209, 6.1.175, 6.6.140, 6.12.86, 6.18.27, 7.0.4, 7.1
- linux Debian 12 6.1.176-1
- linux Debian 13 6.12.86-1
- linux Debian 14 7.0.4-1
debian advisories DEBIAN-CVE-2026-46072
- linux Ubuntu 22.04 LTS 5.15.0-186.196
- linux Ubuntu 24.04 LTS 6.8.0-136.136
- linux Ubuntu 26.04 LTS 7.0.0-27.27
- linux-aws Ubuntu 22.04 LTS 5.15.0-1112.119
- linux-aws Ubuntu 24.04 LTS 6.8.0-1061.64
- linux-aws Ubuntu 26.04 LTS 7.0.0-1008.8
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1112.122
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1064.72
ubuntu advisories UBUNTU-CVE-2026-46072
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
- kernel-source openSUSE Tumbleweed 7.0.11-1.1
opensuse advisories openSUSE-SU-2026:10954-1
- git.kernel.org/stable/c/bbad75336870b51b81979b97613746237fcb02fe commit
- git.kernel.org/stable/c/425de2aba0d061b3e715d51a3b1992c112ed5b99 commit
- git.kernel.org/stable/c/bf7ac4a1d3bfc6e56e54635c3d331a68170d37c9 commit
- git.kernel.org/stable/c/e64f7dfcaff79e7dfff9121a382dd77f9b462f62 commit
- git.kernel.org/stable/c/d3012690a7065d9ca86521a525ad11e8af491d45 commit
- git.kernel.org/stable/c/41aadf5cb482793a24e05aa136224e179a778586 commit
- git.kernel.org/stable/c/b62567bca47408e6739dee75f02a2113548af875 commit
Is CVE-2026-46072 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-46072 updated
kernel: ntfs3: add buffer boundary checks to run_unpack()
-
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.12% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
-
git.kernel.org
/stable/c/bbad75336870b51b81979b97613746237fcb02fe
patch
-
git.kernel.org
/stable/c/425de2aba0d061b3e715d51a3b1992c112ed5b99
patch
-
git.kernel.org
/stable/c/bf7ac4a1d3bfc6e56e54635c3d331a68170d37c9
patch
-
git.kernel.org
/stable/c/e64f7dfcaff79e7dfff9121a382dd77f9b462f62
patch
-
git.kernel.org
/stable/c/d3012690a7065d9ca86521a525ad11e8af491d45
patch
-
git.kernel.org
/stable/c/41aadf5cb482793a24e05aa136224e179a778586
patch
-
git.kernel.org
/stable/c/b62567bca47408e6739dee75f02a2113548af875
patch
Sources
- CVE List CVE-2026-46072
- NVD CVE-2026-46072
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.