Skip to main content
VulnerabilityPublished

CVE-2026-99369: Linux kernel · NFSD: Destroy a recalled delegation the client does not hold

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited : upgrade to d568594503a09ed2761fada2117e4fbaa31972e0 or bbfa823f624d41e85ebca929ac77dc2182cadfed when convenient.

Data as of 19 Nov 2026, 14:34 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in d568594503a09ed2761fada2117e4fbaa31972e0, bbfa823f624d41e85ebca929ac77dc2182cadfed

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Linux kernel to d568594503a09ed2761fada2117e4fbaa31972e0 or bbfa823f624d41e85ebca929ac77dc2182cadfed.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 3bd64a5ba1719c2bb6cba4493dfd3e23a7653e54, < d568594503a09ed2761fada2117e4fbaa31972e0
Fixed in
  • d568594503a09ed2761fada2117e4fbaa31972e0
LinuxLinuxAffected
  • ≥ 3bd64a5ba1719c2bb6cba4493dfd3e23a7653e54, < bbfa823f624d41e85ebca929ac77dc2182cadfed
Fixed in
  • bbfa823f624d41e85ebca929ac77dc2182cadfed
LinuxLinuxAffected
  • =3.10
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: NFSD: Destroy a recalled delegation the client does not hold A client that answers CB_RECALL with NFS4ERR_BADHANDLE or NFS4ERR_BAD_STATEID has no record of the delegation, so the FREE_STATEID that clears it from cl_revoked never arrives. Every later SEQUENCE reply carries SEQ4_STATUS_RECALLABLE_STATE_REVOKED, and the client loops issuing TEST_STATEID. Destroy such a delegation when it is reaped rather than revoking it onto cl_revoked. RFC 8881 Section 20.2.4 completes the recall at the reply when its status is neither NFS4_OK nor NFS4ERR_DELAY, so a rejected recall leaves nothing to revoke. An administrative revoke keeps that path, since NFS4ERR_ADMIN_REVOKED reports it. A destroyed stateid returns NFS4ERR_BAD_STATEID instead of NFS4ERR_DELEG_REVOKED. A client that rejects the recall but still holds the delegation gets no notice that its state was revoked. CB_RECALL can outrun the reply that granted the delegation, so honor a rejection only once the client has seen that grant. Per RFC 8881 Section 2.10.6.3, retirement of the slot that carried the grant is that proof; retry until then, and revoke when the retries lapse.

References

Community reviews

Loading reviews…