CVE-2026-89654

Source
https://cve.org/CVERecord?id=CVE-2026-89654
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89654.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-89654
Downstream
AZL (1)
BELL (1)
CLSA (2)
DEBIAN (1)
openSUSE (1)
UBUNTU (1)
Related
Published
2026-09-11T19:45:44Z
Modified
2026-10-24T02:30:38Z
Severity
  • 9.8 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
Summary
ceph: fix UAF in check_new_map() on session freed during unlock
Details

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

Database specific
{
    "cna_assigner":  "Linux",
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89654.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
2f2dc053404febedc9c273452d9d518fb31fde72
Fixed
352a278d5a1965aae3f817ce5d24a67ee42d45d1
Fixed
820871e9dbeecd2533c4c5f5d91878ceaf02324c
Fixed
9646dfee880730aae4b379a4b8ee6c88ac735acd
Fixed
21d5be092d947f8d83f76f7ebf3989e7e9230a98
Fixed
ee611a7509554c4ca1f54f6aefe592fb1df7ea70

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89654.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
2.6.34
Fixed
6.6.160
Type
ECOSYSTEM
Events
Introduced
6.7.0
Fixed
6.12.114
Type
ECOSYSTEM
Events
Introduced
6.13.0
Fixed
6.18.57
Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
7.2.4

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89654.json"