CVE-2026-22989: nfsd: check that server is running in unlock_filesystem

Published Jan 23, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

nfsd: check that server is running in unlockfilesystem

If we are trying to unlock the filesystem via an administrative interface and nfsd isn't running, it crashes the server. This happens currently because nfsd4revokestates() access state structures (eg., confidhashtbl) that has been freed as a part of the server shutdown.

[ 59.465072] Call trace: [ 59.465308] nfsd4revokestates+0x1b4/0x898 [nfsd] (P) [ 59.465830] writeunlockfs+0x258/0x440 [nfsd] [ 59.466278] nfsctltransactionwrite+0xb0/0x120 [nfsd] [ 59.466780] vfswrite+0x1f0/0x938 [ 59.467088] ksyswrite+0xfc/0x1f8 [ 59.467395] arm64syswrite+0x74/0xb8 [ 59.467746] invokesyscall.constprop.0+0xdc/0x1e8 [ 59.468177] doel0svc+0x154/0x1d8 [ 59.468489] el0svc+0x40/0xe0 [ 59.468767] el0t64synchandler+0xa0/0xe8 [ 59.469138] el0t64sync+0x1ac/0x1b0

Ensure this can't happen by taking the nfsdmutex and checking that the server is still up, and then holding the mutex across the call to nfsd4revokestates().

Affected Software

8 affected componentsFixes available
The Linux Foundation Linux Kernel
Linux Linux kernel>=6.9<6.12.66
Linux Linux kernel>=6.13<6.18.6
Linux Linux kernel=6.19-rc1
Linux Linux kernel=6.19-rc2
Linux Linux kernel=6.19-rc3
Linux Linux kernel=6.19-rc4
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
  2. Compensating control

    In the nfsd filesystem-unlock path, take nfsd_mutex, check that the nfsd server is still running, and hold the mutex across the call to nfsd4_revoke_states().

Event History

Jan 23, 2026
CVE Published
via MITRE·03:24 PM
Data Sourced
via MITRE·03:24 PM
Description
Data Sourced
via NVD·04:15 PM
RemedyDescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-22989?

CVE-2026-22989 is categorized as a high severity vulnerability due to its potential to crash the server.

2

How do I fix CVE-2026-22989?

To fix CVE-2026-22989, ensure that the nfsd service is running before attempting to unlock the filesystem.

3

What impact does CVE-2026-22989 have on system performance?

CVE-2026-22989 can lead to system crashes, affecting availability and stability.

4

Which versions of the Linux Kernel are affected by CVE-2026-22989?

CVE-2026-22989 affects various versions of the Linux Kernel without specific version exclusions.

5

Is CVE-2026-22989 related to filesystem management?

Yes, CVE-2026-22989 is related to filesystem management and how nfsd interacts with the filesystem during unlock operations.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203