# CVE-2023-32256: Kernel: ksmbd race issue from smb2 close and logoff with multichannel

> A race condition in the Linux kernel's ksmbd component allows attackers to trigger a use-after-free, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Aug 2025
- **Updated:** 29 Jun 2026
- **Also known as:** DEBIAN-CVE-2023-32256, GHSA-fmp3-xxcc-559c, ROOT-OS-DEBIAN-11-CVE-2023-32256, UBUNTU-CVE-2023-32256

## What is CVE-2023-32256?

CVE-2023-32256 is a high-severity use after free vulnerability in Red Hat Enterprise Linux 10, published on 1 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in the Linux kernel's ksmbd component. A race condition between smb2 close operation and logoff in multichannel connections could result in a use-after-free issue.

Weakness: CWE-421 (Race Condition During Access to Alternate Channel)

## Which versions are affected by CVE-2023-32256?


## How do I fix CVE-2023-32256?

Apply the vendor's patch.

## Is CVE-2023-32256 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32256 and fix it if it is affected.

What it is: CVE-2023-32256 is a high-severity use after free vulnerability in Red Hat Enterprise Linux 10, published on 1 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-32256 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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-2023-32256/ (Markdown: https://insights.sbomify.com/CVE-2023-32256/index.md)
```

## Sources

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

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