CVE-2026-99107
ntfs: fix incorrect MFT record pointer passed to ntfs_attr_record_resize
No exploitation reported by the sources we read.
- Published2026-10-28
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
In the Linux kernel, the following vulnerability has been resolved: ntfs: fix incorrect MFT record pointer passed to ntfs_attr_record_resize ntfs_new_attr_flags() passes the wrong MFT record to ntfs_attr_record_resize(). When the attribute is in an extent record, ctx->mrec points to the extent but the function receives the base record pointer m, causing incorrect size calculations in memmove. Fix by passing ctx->mrec (the actual MFT record containing the attribute) instead of m (the base MFT record) to ntfs_attr_record_resize().
Timeline
dates in UTC- 2026-10-2811:17CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-31 15:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-99107?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-99107?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
- CVE-2026-99107 Red Hat Product Security
kernel: ntfs: fix incorrect MFT record pointer passed to ntfs_attr_record_resize
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVE recordread 2026-10-31
- CNACVSS 3.17.8read 2026-10-31
- FIRST EPSSEPSS score0.2 %2026-10-30
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2026-10-28
- Last Modified
- 2026-10-31
- NVD status
- Received
Frequently asked questions
What is CVE-2026-99107?
Is CVE-2026-99107 actively exploited?
What is the CVSS score for CVE-2026-99107?
Running Linux kernel? Hear about its next vulnerability
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
- CVE-2026-76418KEVsame weekCisco Secure Firewall Adaptive Security Appliance and Secure Firewall Threat Defense Software Remote Access SSL VPN Tunnel Denial of Service Vulnerability
- CVE-2026-86379same week
- CVE-2026-116505same weekTOTOLINK A950RG device-information udhcpd.leases getDeviceInfo command injection
- CVE-2026-112351same week
- CVE-2026-116485same week
- CVE-2026-93680same weekLangflow OSS is affected by multiple vulnerabilities
- CVE-2026-86394same week
- CVE-2026-86399same week