{ "schema_version": "1.6.1", "id": "RPI-CVE-2026-89692", "modified": "2026-10-09T11:39:44Z", "upstream": [ "CVE-2026-89692" ], "published": "2026-09-11T19:47:07Z", "summary": "nfsd: clear CALLBACK_RUNNING on failed delegation recall queue", "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: clear CALLBACK_RUNNING on failed delegation recall queue\n\nnfsd_break_one_deleg() sets NFSD4_CALLBACK_RUNNING via test_and_set_bit\nat entry to serialize recall work, then calls nfsd4_run_cb() to queue\nthe recall. When the queue attempt fails the refcount bump is undone,\nbut the RUNNING bit is left set. The only site that clears the bit is\nnfsd41_destroy_cb() (fs/nfsd/nfs4callback.c), which runs from the\nworkqueue and is therefore unreachable when nothing was queued.\n\nThe bit becomes a permanent latch on dp->dl_recall.cb_flags: every\nsubsequent break_lease() on the same delegation hits the early-return\nguard in nfsd_break_one_deleg() and silently skips the recall, so the\ndelegation is never broken and the conflicting open or lock stalls.\n\nFix by clearing NFSD4_CALLBACK_RUNNING on the !queued branch alongside\nthe refcount_dec.", "severity": [ { "type": "CVSS_V3", "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H" } ], "affected": [ { "package": { "ecosystem": "Raspberry Pi OS:13", "name": "linux" }, "versions": [ "1:6.18.29-1+rpt1", "1:6.18.33-1+rpt1", "1:6.18.34-1+rpt1", "1:6.18.39-1+rpt1" ], "ecosystem_specific": { "binaries": [ { "binary_name": "linux-image-6.18.29+rpt-rpi-2712", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.29+rpt-rpi-v6", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.29+rpt-rpi-v7", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.29+rpt-rpi-v8", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.29+rpt-rpi-v8-rt", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-2712", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v6", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v7", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v8", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v8-rt", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-2712", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v6", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v7", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v8", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v8-rt", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-2712", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v6", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v7", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v8", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v8-rt", "binary_version": "1:6.18.39-1+rpt1" } ] }, "database_specific": { "per_version": { "1:6.18.29-1+rpt1": { "linux_commit": "66318c5b5cd8145a662303af12ed39ac07eb27cc", "upstream_version": "6.18.29", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.50" }, "1:6.18.33-1+rpt1": { "linux_commit": "95b85bebbedcaedfa7ca79116ed38b7376fba412", "upstream_version": "6.18.33", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.50" }, "1:6.18.34-1+rpt1": { "linux_commit": "c8c7494100e99ee05b11aaa4f0588a223a63d1af", "upstream_version": "6.18.34", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.50" }, "1:6.18.39-1+rpt1": { "linux_commit": "60ea684a8ace97bb0db1a16e20753bdd6ab371ff", "upstream_version": "6.18.39", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.50" } } } } ], "references": [ { "type": "ADVISORY", "url": "https://www.cve.org/CVERecord?id=CVE-2026-89692" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/b137930ee52e3ef38915a3511d4c070463b63a32" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/cb2d0c4d1b3d301d042ed61365eaa8cb0141a254" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/b036727d334b1b7cd4c1f1fba3b59ba93a6bbe96" } ], "database_specific": { "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git", "upstream_modified": "2026-09-13T06:49:25Z", "severity": { "source": "kernel CNA", "cvss_v3_score": 7.5, "cvss_v3_severity": "High", "scenario": "AV:N - nfsd_break_one_deleg() runs in in-kernel nfsd (fs/nfsd/nfs4state.c) and is reached over TCP/2049 via svc_process to nfsd_dispatch to nfsd4_proc_compound: a remote NFSv4 OPEN grants a delegation, then a conflicting OPEN hits nfsd_file_acquire/nfsd_open_break_lease to __break_lease to nfsd_break_deleg_cb().\nAC:L - The attacker drives both sides with two NFSv4 clients: one holds the delegation while the other sends conflicting OPEN/LOCK/SETATTR to invoke nfsd_break_one_deleg(), and can DESTROY_CLIENTID or flap the backchannel so queue_work() fails; the sequence is retryable and needs no uninfluenced memory layout.\nPR:N - Default AUTH_SYS/AUTH_NULL nfsd exports do not cryptographically verify RPC credentials; any host allowed by the export can EXCHANGE_ID/SETCLIENTID, OPEN to receive a delegation, and issue a conflicting OPEN with no local Linux account or capability.\nUI:N - The attacking NFS clients send the OPEN, conflicting OPEN, and optional DESTROY_CLIENTID RPCs themselves; no victim user on the NFS server must mount a filesystem, open a file, or otherwise interact at attack time.\nS:U - The latched NFSD4_CALLBACK_RUNNING bit and stalled lease-break live in kernel nfsd/VFS state on the NFS server; this is not a VM, IOMMU, or sandbox boundary crossing.\nC:N - The bug only leaves NFSD4_CALLBACK_RUNNING set so later recalls are skipped; it does not read attacker-inaccessible kernel memory, leak pointers, or return extra data to the client.\nI:N - There is no use-after-free, out-of-bounds write, or other memory corruption, and conflicting writers are blocked rather than committing unauthorized file changes, so integrity is unaffected.\nA:H - When nfsd4_run_cb() fails, RUNNING stays set, later break_lease() skips CB_RECALL, nfsd4_cb_recall_prepare never queues the delegation on del_recall_lru, and fl_break_time is zeroed so VFS will not expire the lease; conflicting opens/locks then stall or retry NFS4ERR_JUKEBOX indefinitely, denying the file and NFS service." } } }