cve.bz

CVE-2026-99171 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: ntfs3: free the sbi after a grace period If the "nocase" mount option ntfs3 uses custom hash and dentry compare functions. Both access ntfs3 superblock private information in rcu pathwalk. ntfs_put_super() and ntfs3_kill_sb() drop the info without any rcu delay. A lookup that's still inside the filesystem when the last reference to the mount is dropped causes a UAF. With a pathwalk held up in ntfs_d_hash() while the last reference to the mount goes away: BUG: KASAN: slab-use-after-free in ntfs_nls_to_utf16+0x752/0x940 Read of size 8 at addr ff1100010453c850 by task walker/99 Call Trace: <TASK> ntfs_nls_to_utf16+0x752/0x940 ntfs_d_hash+0x22b/0x500 link_path_walk+0x11ad/0x1d30 path_lookupat+0x63/0xb00 filename_lookup+0x1f1/0x5b0 vfs_statx+0xd7/0x3b0 [...] Allocated by task 95: __kmalloc_cache_noprof+0x249/0x560 ntfs_init_fs_context+0x2db/0x5a0 alloc_fs_context+0x52e/0xc70 [...] Freed by task 98: kfree+0x1db/0x5b0 deactivate_locked_super+0x9c/0xf0 cleanup_mnt+0x9f/0x130 task_work_run+0x131/0x250 The bug is currently masked by the grace period in namespace_unlock() for umount(2). Keep the necessary information until the filesystem private info is freed and free it with an rcu delay. ntfs3_free_sbi() now runs from an rcu callback and drops the upcase table via ntfs_put_shared(). So switch s_shared_lock over to spin_lock_bh(). Otherwise the callback can deadlock against a task holding the lock on the same cpu.
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 6.6.161
  • Linux Linux: fixed in 6.12.115
  • Linux Linux: fixed in 6.18.59
  • Linux Linux: fixed in 7.2.13
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-99171 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99171?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99171?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-99171 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.2 and later

Fixed in

ProductRelease lineFixed in
Linux6.66.6.161
Linux6.126.12.115
Linux6.186.18.59
Linux7.27.2.13
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2026-99171
Debian13linux6.12.115-2DEBIAN-CVE-2026-99171
Debian14linux7.2.13-1DEBIAN-CVE-2026-99171
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-99171
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-99171
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-99171
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 40 moreno fix listedUBUNTU-CVE-2026-99171
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 50 moreno fix listedUBUNTU-CVE-2026-99171
Ubuntu26.04:LTSlinux, linux-aws, linux-gcp and 12 moreno fix listedUBUNTU-CVE-2026-99171
Ubuntu26.10linux7.3.0-10.10UBUNTU-CVE-2026-99171
Ubuntu26.10linux-aws, linux-gcp, linux-azure and 2 more7.3.0-1004.4UBUNTU-CVE-2026-99171
Ubuntu26.10linux-azure-fde7.3.0-1004.5UBUNTU-CVE-2026-99171
Ubuntu26.10linux-riscv, linux-realtime7.3.0-10.10.1UBUNTU-CVE-2026-99171
UbuntuNvidia-BlueField:24.04:LTSlinux-bluefieldno fix listedUBUNTU-CVE-2026-99171
UbuntuPro:FIPS-updates:24.04:LTSlinux-fips, linux-aws-fips, linux-gcp-fips and 1 moreno fix listedUBUNTU-CVE-2026-99171
2 more for Ubuntu in the JSON and on Ubuntu's page.
Azure Linux3kernel6.6.161.1-1AZL-111320
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-99171
Alpaquitastreamlinux-lts6.18.62-r0BELL-CVE-2026-99171

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Not affected
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-99171.

References

Check your stackJSON