CVE-2026-89712
Last modified
CVE-2026-89712 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: NFSD: restart ssc_expire_umount walk after dropping nfsd_ssc_lock nfsd4_ssc_expire_umount() walks nn->nfsd_ssc_mount_list with list_for_each_entry_safe(ni, tmp, ...). For each expired entry it sets nsui_busy = true, drops nfsd_ssc_lock to run mntput() on the source vfsmount, then reacquires the lock to list_del + kfree the entry and continue iterating via the macro's saved tmp pointer. The nsui_busy flag protects the current ni from concurrent nfsd4_ssc_setup_dul() finders during the lock-drop window, but it does not pin tmp. EPSS estimates a 0.63% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: NFSD: restart ssc_expire_umount walk after dropping nfsd_ssc_lock nfsd4_ssc_expire_umount() walks nn->nfsd_ssc_mount_list with list_for_each_entry_safe(ni, tmp, ...). For each expired entry it sets nsui_busy = true, drops nfsd_ssc_lock to run mntput() on the source vfsmount, then reacquires the lock to list_del + kfree the entry and continue iterating via the macro's saved tmp pointer. The nsui_busy flag protects the current ni from concurrent nfsd4_ssc_setup_dul() finders during the lock-drop window, but it does not pin tmp. Another nfsd RPC thread that fails its source- server mount and reaches nfsd4_ssc_cancel_dul() will, during that same window, take nfsd_ssc_lock, list_del + kfree its own ssc_umount item, and release the lock. If that item is the saved tmp of the expire walk, the next iteration dereferences a freed nfsd4_ssc_umount_item. Restart the walk from the head after the mntput() unlock window so no saved next pointer survives the lock-drop. The list is bounded by the number of active inter-server source mounts (typically small) and the expire delayed-work runs periodically rather than per-IO, so the restart is cheap.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= a4bc287943f5695209ff36bdc89f17b48d68fae7, < 2b59029b8f24a99b5d844af2da3950d39d36eeea; >= f4e44b393389c77958f7c58bf4415032b4cda15b, < d9e151fea5ed706c1284adacabd869b0be745db2; >= f4e44b393389c77958f7c58bf4415032b4cda15b, < 659ee3da073164e1e6e40dfcbc26eeed85845f93; >= f4e44b393389c77958f7c58bf4415032b4cda15b, < 60680ae7243b22de3d09be990d8e23bcfc4af837; >= f4e44b393389c77958f7c58bf4415032b4cda15b, < 77de363d9a1c8cd35f20482782c612cda085791a; >= f4e44b393389c77958f7c58bf4415032b4cda15b, < 4ed8d2317aef21cc2a9e5a55d6b59860b4b151a8; >= f4e44b393389c77958f7c58bf4415032b4cda15b, < 7377fa964b8aaf47cb04e5efcc4c82d15e8c2ce9; >= f4e44b393389c77958f7c58bf4415032b4cda15b, < 036c1b182f4da65363e79ec0ac276edc6b7296e5; >= 5.10.220, < 5.10.270 |
| Linux | Linux | 5.14 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-89712?
How severe is CVE-2026-89712?
How do I fix CVE-2026-89712?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-89707In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-89708In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-89709In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-8971Same-origin policy bypass in the Networking: JAR component. …6.5
- CVE-2026-89710In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89711In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-89713In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-89714In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89715In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89716In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89717In the Linux kernel, the following vulnerability has been re…
- CVE-2026-89718In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-89712?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
