Vulnerability · Published Sep 11, 2026 · Assigned by Linux
CVE-2026-89689nfsd: don't free session slots that are still in use
Critical 9.8
In plain English
A critical-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.6% (higher than 50% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| AlmaLinux:10 | kernel | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-64k | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-64k-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-64k-debug | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-64k-debug-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-64k-debug-devel | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-64k-debug-modules | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-64k-devel | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-64k-devel-matched | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-64k-modules | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-64k-modules-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-64k-modules-extra | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-abi-stablelists | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-cross-headers | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-debug | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-debug-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-debug-devel | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-debug-devel-matched | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-debug-modules | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-debug-modules-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-debug-modules-extra | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-debug-uki-virt | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-devel | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-devel-matched | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-doc | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-headers | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-modules | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-modules-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-modules-extra | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-modules-extra-matched | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-64k | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-64k-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-64k-debug | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-64k-debug-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-64k-debug-devel | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-64k-debug-modules | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-64k-debug-modules-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-64k-debug-modules-extra | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-64k-devel | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-64k-modules | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-64k-modules-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-64k-modules-extra | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-debug | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-debug-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-debug-devel | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-debug-modules | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-debug-modules-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-debug-modules-extra | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-devel | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-modules | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-modules-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-rt-modules-extra | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-tools | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-tools-libs | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-tools-libs-devel | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-uki-virt | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-uki-virt-addons | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-zfcpdump | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-zfcpdump-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-zfcpdump-devel | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-zfcpdump-devel-matched | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-zfcpdump-modules | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-zfcpdump-modules-core | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | kernel-zfcpdump-modules-extra | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | libperf | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | perf | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | python3-perf | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | rtla | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| AlmaLinux:10 | rv | 6.12.0-211.66.1.el10_2 | ALSA-2026:83207 |
| Debian:14 | linux | 7.2.6-1 | DEBIAN-CVE-2026-89689 |
| Rocky Linux:10 | kernel | 0:6.12.0-211.66.1.el10_2 | RLSA-2026:83207 |
| Ubuntu:26.04:LTS | linux | 7.0.0-42.42 | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:26.04:LTS | linux-aws | 7.0.0-1016.17 | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-aws-7.0 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:26.04:LTS | linux-azure | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-azure-7.0 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:26.04:LTS | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.17 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-azure-fde-7.0 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:26.04:LTS | linux-gcp | 7.0.0-1016.18 | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-gcp-7.0 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:26.04:LTS | linux-gke | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-hwe-7.0 | 7.0.0-42.42~24.04.1 | UBUNTU-CVE-2026-89689 |
| Ubuntu:26.04:LTS | linux-ibm | 7.0.0-1017.17 | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:26.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-nvidia-7.0 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:26.04:LTS | linux-nvidia-bos | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:26.04:LTS | linux-oem-7.0 | 7.0.0-1017.17 | UBUNTU-CVE-2026-89689 |
| Ubuntu:26.04:LTS | linux-oracle | 7.0.0-1015.16 | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-oracle-7.0 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:26.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:26.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:26.04:LTS | linux-riscv | 7.0.0-42.42.1 | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:24.04:LTS | linux-riscv-7.0 | 7.0.0-42.42.1~24.04.1 | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-89689 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-89689 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | fc8738c68d0bbf5033dd98b4f63d277ecbd49fd7 – before 72d40b103bb03f0124d3a3c8f71a30cbafaf6afafc8738c68d0bbf5033dd98b4f63d277ecbd49fd7 – before b449b134e7762ddf98653a4b1d3e76d2d212ea64fc8738c68d0bbf5033dd98b4f63d277ecbd49fd7 – before f5d22e372f4ac3eb287037a488c29691d52a6330 |
| Linux | Linux | 6.14 |