Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-89712

NFSD: restart ssc_expire_umount walk after dropping nfsd_ssc_lock

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 38 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-89712, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.71% · top 46% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected a4bc287943f5695209ff36bdc89f17b48d68fae7 – < 2b59029b8f24a99b5d844af2da3950d39d36eeea
    • affected f4e44b393389c77958f7c58bf4415032b4cda15b – < d9e151fea5ed706c1284adacabd869b0be745db2
    • affected f4e44b393389c77958f7c58bf4415032b4cda15b – < 659ee3da073164e1e6e40dfcbc26eeed85845f93
    • affected f4e44b393389c77958f7c58bf4415032b4cda15b – < 60680ae7243b22de3d09be990d8e23bcfc4af837
    • affected f4e44b393389c77958f7c58bf4415032b4cda15b – < 77de363d9a1c8cd35f20482782c612cda085791a
    • affected f4e44b393389c77958f7c58bf4415032b4cda15b – < 4ed8d2317aef21cc2a9e5a55d6b59860b4b151a8
    • affected f4e44b393389c77958f7c58bf4415032b4cda15b – < 7377fa964b8aaf47cb04e5efcc4c82d15e8c2ce9
    • affected f4e44b393389c77958f7c58bf4415032b4cda15b – < 036c1b182f4da65363e79ec0ac276edc6b7296e5
    • affected 5.10.220 – < 5.10.270
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89712 badge
[![CVE-2026-89712](https://cveledger.app/badge/CVE-2026-89712.svg)](https://cveledger.app/cve/CVE-2026-89712)

Record last updated .