ceph: fix UAF in check_new_map() on session freed during unlock
CVE-2026-89654 · published 11 Sept 2026
How serious is it
- Severity: critical, CVSS score 9.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-89654?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 2f2dc053404febedc9c273452d9d518fb31fde72 to < 352a278d5a1965aae3f817ce5d24a67ee42d45d1, 2f2dc053404febedc9c273452d9d518fb31fde72 to < 820871e9dbeecd2533c4c5f5d91878ceaf02324c, 2f2dc053404febedc9c273452d9d518fb31fde72 to < 9646dfee880730aae4b379a4b8ee6c88ac735acd, 2f2dc053404febedc9c273452d9d518fb31fde72 to < 21d5be092d947f8d83f76f7ebf3989e7e9230a98
- Linux Linux: 2.6.34
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
ceph: fix UAF in check_new_map() on session freed during unlock
check_new_map() iterates mdsc->sessions[] and for each active session
drops mdsc->mutex to perform per-session operations. The forced-close
path (rank removed from map) correctly takes a reference on s via
ceph_get_mds_session() before releasing mdsc->mutex, but three other
paths do not:
Path A (address changed): mutex_unlock → mutex_lock(&s->s_mutex)
Path B (reconnect): mutex_unlock → send_mds_reconnect(mdsc, s)
Path C (active transition): mutex_unlock → mutex_lock(&s->s_mutex)
Without the extra reference, another thread can acquire mdsc->mutex
during the unlock window, call __unregister_session() which drops the
last reference on s, and free it. The original thread then accesses
freed memory via s->s_mutex.
Fix by adding ceph_get_mds_session(s) before each mutex_unlock and
ceph_put_mds_session(s) after the corresponding mutex_lock, matching
the pattern already used in the forced-close path.
Race timeline (Path A):
Thread A (check_new_map) Thread B (another map update
holds mdsc->mutex or session teardown)
-------------------------- --------------------------
s = mdsc->sessions[i]
(refcount == 1, held only by
sessions[] array)
mutex_unlock(&mdsc->mutex)
---> acquires mdsc->mutex
__unregister_session(mdsc, s)
sessions[i] = NULL
ceph_put_mds_session(s)
refcount: 1 -> 0
kfree(s) <--- freed!
mutex_lock(&s->s_mutex)
UAF on freed s->s_mutex
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/352a278d5a1965aae3f817ce5d24a67ee42d45d1
- git.kernel.org/stable/c/820871e9dbeecd2533c4c5f5d91878ceaf02324c
- git.kernel.org/stable/c/9646dfee880730aae4b379a4b8ee6c88ac735acd
- git.kernel.org/stable/c/21d5be092d947f8d83f76f7ebf3989e7e9230a98
- git.kernel.org/stable/c/ee611a7509554c4ca1f54f6aefe592fb1df7ea70
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON