# CVE-2023-52732: ceph: blocklist the kclient when receiving corrupted snap trace

> A corrupted snap trace in the Ceph kernel client can cause the client to be blocked and evicted, leading to 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:** 21 May 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-67734, BELL-CVE-2023-52732, DEBIAN-CVE-2023-52732, GHSA-fwq5-vg2m-5cr5, ROOT-OS-DEBIAN-11-CVE-2023-52732, ROOT-OS-UBUNTU-2204-CVE-2023-52732, UBUNTU-CVE-2023-52732

## What is CVE-2023-52732?

CVE-2023-52732 is a critical denial of service vulnerability in Linux kernel, published on 21 May 2024. 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:

ceph: blocklist the kclient when receiving corrupted snap trace

When received corrupted snap trace we don't know what exactly has
happened in MDS side. And we shouldn't continue IOs and metadatas
access to MDS, which may corrupt or get incorrect contents.

This patch will just block all the further IO/MDS requests
immediately and then evict the kclient itself.

The reason why we still need to evict the kclient just after
blocking all the further IOs is that the MDS could revoke the caps
faster.

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2023-52732 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-52732 is a critical denial of service vulnerability in Linux kernel, published on 21 May 2024. 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-52732 in the wild and no public exploit code.

Affected product: Linux kernel. 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-52732/ (Markdown: https://insights.sbomify.com/CVE-2023-52732/index.md)
```

## Sources

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

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