Skip to content
Threat Brief

← All advisories

CVE-2026-99354

Severity unknownNo known exploitationFix available

sunrpc: pin gss module across auth_domain RCU free

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 10% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In the Linux kernel, the following vulnerability has been resolved: sunrpc: pin gss module across auth_domain RCU free A gss auth_domain stores a raw pointer to svcauthops_gss in dom->flavour, and its release queues svcauth_gss_domain_release_rcu() via call_rcu(). Both live in auth_rpcgss.ko text, and nothing pins the module while a domain referencing it is reachable. rmmod auth_rpcgss can therefore unmap that text while an NFSD export still holds a reference to the domain. The export cache is one such holder. When the export is finally released, the domain reference drops from module text: svc_export_put() auth_domain_put(exp->ex_client) auth_domain_release() dom->flavour->domain_release(dom) /* into module text */ svcauth_gss_domain_release() call_rcu(&dom->rcu_head, svcauth_gss_domain_release_rcu) Once auth_rpcgss is unloaded, the domain_release call lands in unmapped memory. The rcu_barrier() in exit_rpcsec_gss() does not help: it waits only for callbacks already queued, and this one is not queued until the export goes away. NFSD's NFSv4 objects import symbols from auth_rpcgss.ko, so only a server built without CONFIG_NFSD_V4 can unload auth_rpcgss while exports still name a gss domain. Take a module reference in svcauth_gss_register_pseudoflavor() before publishing the domain and drop it at the end of svcauth_gss_domain_release_rcu(). The rcu_barrier() then holds the module image until this callback has returned. [ cel: rewrote description ]

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 608a0ab2f54ab0e301ad76a41aad979ea0d02670 before f735700c06303335067a49ad4ad8f0b60eb43897f735700c06303335067a49ad4ad8f0b60eb43897CVE Program
LinuxLinuxfrom 608a0ab2f54ab0e301ad76a41aad979ea0d02670 before 1c582f719010b5ff9f678cf8307594be0570831b1c582f719010b5ff9f678cf8307594be0570831bCVE Program
LinuxLinuxfrom 608a0ab2f54ab0e301ad76a41aad979ea0d02670 before b64d21116374688c33302a6704387c27d1156d72b64d21116374688c33302a6704387c27d1156d72CVE Program
LinuxLinuxfrom 608a0ab2f54ab0e301ad76a41aad979ea0d02670 before 0cbdbf26c456ef6ad1260dbd1b772239ce7bd0710cbdbf26c456ef6ad1260dbd1b772239ce7bd071CVE Program
LinuxLinux4.20Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.117 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.61 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.2 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program
LinuxLinux (unaffected)all versions before 4.20Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references