ceph: fix UAF in check_new_map() on session freed during unlock
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel ee611a7509554c4ca1f54f6aefe592fb1df7ea70, Kernel 21d5be092d947f8d83f76f7ebf3989e7e9230a98, Kernel 352a278d5a1965aae3f817ce5d24a67ee42d45d1 and 8 more.
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
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=2f2dc053404febedc9c273452d9d518fb31fde72 <ee611a7509554c4ca1f54f6aefe592fb1df7ea70, >=2f2dc053404febedc9c273452d9d518fb31fde72 <21d5be092d947f8d83f76f7ebf3989e7e9230a98, >=2f2dc053404febedc9c273452d9d518fb31fde72 <352a278d5a1965aae3f817ce5d24a67ee42d45d1, >=2f2dc053404febedc9c273452d9d518fb31fde72 <820871e9dbeecd2533c4c5f5d91878ceaf02324c, >=2f2dc053404febedc9c273452d9d518fb31fde72 <9646dfee880730aae4b379a4b8ee6c88ac735acd, >=2f2dc053404febedc9c273452d9d518fb31fde72 <989343b7ee5b1a08778be0c7c4bf6030d3910807, =2.6.34 | ee611a7509554c4ca1f54f6aefe592fb1df7ea70, 21d5be092d947f8d83f76f7ebf3989e7e9230a98, 352a278d5a1965aae3f817ce5d24a67ee42d45d1, 820871e9dbeecd2533c4c5f5d91878ceaf02324c, 9646dfee880730aae4b379a4b8ee6c88ac735acd, 989343b7ee5b1a08778be0c7c4bf6030d3910807 |
| linux-kernel: Kernel | >=6.13.0 <6.18.57, >=6.19.0 <7.2.4, >=6.2.0 <6.6.160, >=6.7.0 <6.12.114, >=2.6.34 <6.1.191 | 6.18.57, 7.2.4, 6.6.160, 6.12.114, 6.1.191 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket