Answer in brief
CVE-2026-89691 records a Unknown severity vulnerability in nfsd: clear opcnt on compound arg release to prevent OOB read. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=bd9d6a3efa9709e653aafbeb859289feccb8e70c <58bcdfb2b2e412088839ae740b1a95154dc0b8d0 || >=bd9d6a3efa9709e653aafbeb859289feccb8e70c <e879148867bd4c4cac42e063ffaffa187dddc6fe || >=bd9d6a3efa9709e653aafbeb859289feccb8e70c <c1a4f7b1848f95302df598217e1c7a1410c2d0c5 || >=bd9d6a3efa9709e653aafbeb859289feccb8e70c <ae4c38555e81563b8dc5eae55ffd70f0ea97aa5a | 58bcdfb2b2e412088839ae740b1a95154dc0b8d0, e879148867bd4c4cac42e063ffaffa187dddc6fe, c1a4f7b1848f95302df598217e1c7a1410c2d0c5, ae4c38555e81563b8dc5eae55ffd70f0ea97aa5a |
| Linux/Linuxgeneric | 6.7 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
In the Linux kernel, the following vulnerability has been resolved: nfsd: clear opcnt on compound arg release to prevent OOB read nfsd4_release_compoundargs() resets args->ops to the inline iops[8] array when the dynamically-allocated ops buffer is freed, but leaves args->opcnt at its original value (which can be up to 200 for NFSv4.1+ compounds). If rq_status_counter is stuck at an odd value (which can happen when nfsd_dispatch() hits an error path after setting it odd), the RPC status dumpit handler reads min(opcnt, 16) entries from args->ops[]. Since iops only has 8 elements and is the last field in struct nfsd4_compoundargs, reading indices 8-15 accesses adjacent slab memory and leaks it to userspace via netlink. Zero opcnt unconditionally in nfsd4_release_compoundargs() so stale compound metadata is never exposed through the status interface. [ cel: Remove the kvfree_rcu_mightsleep() sleep from the exposure window ]
Quoted source text, attributed separately from HOL analysis.