# CVE-2023-53751: cifs: fix potential use-after-free bugs in TCP_Server_Info::hostname

> A use-after-free vulnerability in the Linux kernel CIFS module allows attackers to potentially execute code or cause a denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 8 Dec 2025
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2023-53751, DEBIAN-CVE-2023-53751, GHSA-7gp2-6wc7-fw9f, ROOT-OS-DEBIAN-11-CVE-2023-53751, ROOT-OS-UBUNTU-2204-CVE-2023-53751, UBUNTU-CVE-2023-53751

## What is CVE-2023-53751?

CVE-2023-53751 is a critical use after free vulnerability in Linux, published on 8 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

cifs: fix potential use-after-free bugs in TCP_Server_Info::hostname

TCP_Server_Info::hostname may be updated once or many times during
reconnect, so protect its access outside reconnect path as well and
then prevent any potential use-after-free bugs.

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


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

Apply the vendor's patch.

## Is CVE-2023-53751 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-53751 is a critical use after free vulnerability in Linux, published on 8 Dec 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-53751 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-2023-53751/ (Markdown: https://insights.sbomify.com/CVE-2023-53751/index.md)
```

## Sources

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

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