# CVE-2026-98450: smb: client: close completed creates on compound wait errors

> A flaw in the Linux kernel SMB client fails to close remote handles on compound wait errors, potentially leading to resource exhaustion and denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-108717, BELL-CVE-2026-98450, DEBIAN-CVE-2026-98450, GHSA-vqm5-qg35-949v, UBUNTU-CVE-2026-98450

## What is CVE-2026-98450?

CVE-2026-98450 is a denial of service vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

smb: client: close completed creates on compound wait errors

compound_send_recv() waits for responses in order. If a later wait is
interrupted, or if a later MID fails during response synchronization, an
earlier CREATE may already have opened a remote handle. The earlier mid
is then released without invoking handle_cancelled_mid(), leaving the
remote handle open because no FID was copied to the caller.

Mark completed earlier mids as cancelled when a compound wait or MID
synchronization aborts. Keep their response buffers attached while the
MIDs are synchronized, and transfer them only after synchronization of
the processed responses, so the release path can inspect successful
CREATE responses and queue SMB2_close() after a later failure. Account for
a remote open only after the close work is allocated and before it is
queued, since the caller has not yet updated num_remote_opens. Mark the
create+close compound used by smb2_unlink() so it is not closed again.
Non-CREATE responses and compounds that already include a close keep their
existing behavior.

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


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

Apply the vendor's patch.

## Is CVE-2026-98450 being exploited?

There is no known exploitation of CVE-2026-98450 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98450 and fix it if it is affected.

What it is: CVE-2026-98450 is a denial of service vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98450 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98450/ (Markdown: https://insights.sbomify.com/CVE-2026-98450/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98450
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98450
- OSV: https://osv.dev/vulnerability/CVE-2026-98450

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98450/
Summaries are generated and may contain mistakes; the official description above is the record.