CVE-2026-89689
nfsd: don't free session slots that are still in use
Reported by linux · Published September 11, 2026
In the Linux kernel, the following vulnerability has been resolved: nfsd: don't free session slots that are still in use nfsd4_sequence() can free the very slot it is currently processing. When the session shrinker has reduced se_target_maxslots below se_fchannel.maxreqs, the shrink path checks three conditions before calling free_session_slots(): 1. se_target_maxslots < maxreqs (shrink was advertised) 2. slot->sl_generation == se_slot_gen (slot is up-to-date) 3. seq->maxslots <= se_target_maxslots (client acknowledges) However, seq->slotid is never checked against se_target_maxslots. A client using a slot in the range [se_target_maxslots, maxreqs) can satisfy all three conditions: its slot has the current generation (set by a prior SEQUENCE), and it sends sa_highest_slotid <= se_target_maxslots to acknowledge the reduction. free_session_slots() then kfrees every slot at index >= se_target_maxslots, including the caller's own slot. The function continues to write sl_seqid, sl_flags, sl_generation, and stores the dangling pointer in cstate->slot. Later, nfsd4_store_cache_entry() copies up to maxresp_cached bytes of the compound reply into the freed sl_data[] array, corrupting whatever slab object now occupies that address. Additionally, a concurrent thread processing SEQUENCE on a different high-numbered slot can have its slot freed out from under it. NFSD4_SLOT_INUSE is set under nn->client_lock before the lock is released, so any concurrent thread past SEQUENCE will have its slot marked. However, free_session_slots() does not check NFSD4_SLOT_INUSE before freeing. Fix both problems by: 1. Checking that the current request's slotid is below the shrink boundary. 2. Scanning slots in the to-be-freed range for NFSD4_SLOT_INUSE and deferring the shrink if any are active.
EPSS 0.61% · 50.3th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| libperf | errata.rockylinux.org | 6.12.0-211.66.1.el10 |
| perf-debuginfo | errata.rockylinux.org | 6.12.0-211.66.1.el10 |
| kernel-abi-stablelists | errata.rockylinux.org | 6.12.0-211.66.1.el10 |
| kernel-doc | errata.rockylinux.org | 6.12.0-211.66.1.el10 |
| perf | errata.rockylinux.org | 6.12.0-211.66.1.el10 |
| kernel-rt-debug-modules | errata.rockylinux.org | 6.12.0-211.66.1.el10 |
| kernel-modules | errata.rockylinux.org | 6.12.0-211.66.1.el10 |
| libperf-debuginfo | errata.rockylinux.org | 6.12.0-211.66.1.el10 |
| kernel-rt | errata.rockylinux.org | 6.12.0-211.66.1.el10 |
| rv | errata.rockylinux.org | 6.12.0-211.66.1.el10 |
| kernel-uki-virt-addons | errata.rockylinux.org | 6.12.0-211.66.1.el10 |
| kernel-tools-debuginfo | errata.rockylinux.org | 6.12.0-211.66.1.el10 |
51 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | fc8738c68d0bbf5033dd98b4f63d277ecbd49fd7, fc8738c68d0bbf5033dd98b4f63d277ecbd49fd7, fc8738c68d0bbf5033dd98b4f63d277ecbd49fd7 |
| Linux | Linux | 6.14, 0, 6.18.50 |
| amazon:2023 | kernel6.18-tools | 0 |
| amazon:2023 | kernel-livepatch-6.18.51-120.162 | 0 |
| amazon:2023 | kernel6.18-modules-extra-common | 0 |
| amazon:2023 | kernel6.18-devel | 0 |
| amazon:2023 | bpftool6.18 | 0 |
| amazon:2023 | kernel6.18-tools-devel | 0 |
| amazon:2023 | microvm-kernel6.18 | 0 |
| amazon:2023 | python3-perf6.18 | 0 |
| amazon:2023 | kernel6.18-modules-extra | 0 |
| linux | linux_kernel | 6.14, 6.14, 6.14 |
| amazon:2023 | kernel6.18 | 0 |
| Linux | Linux | 7.3, *, * |
| amazon:2023 | kernel6.18-headers | 0 |
| amazon:2023 | perf6.18 | 0 |
Timeline
- Sep 11, 2026 CVE Published
- Sep 12, 2026 EPSS Score (29 in total, the first dated here)
- Oct 19, 2026 CVE Updated
- Oct 23, 2026 Distribution Patch (2 in total, the first dated here)
- Oct 23, 2026 Security Advisory (2 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-89689
vulnetix vdb fixes CVE-2026-89689
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-89689/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart