libceph: refresh auth->authorizer_buf{,_len} after authorizer update
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.5, 3.10, 5.10.265, 5.15.216, 6.1.183, and 4 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: libceph: refresh auth->authorizer_buf{,_len} after authorizer update ceph_x_create_authorizer() caches au->buf->vec.iov_base and au->buf->vec.iov_len in struct ceph_auth_handshake. These cached values are then used by the messenger connect code when sending the authorizer. ceph_x_update_authorizer() can rebuild the authorizer when a newer service ticket is available. If the rebuilt authorizer no longer fits in the existing buffer, ceph_x_build_authorizer() drops its reference to au->buf and allocates a new one. If this is the final reference, ceph_buffer_put() frees the old ceph_buffer and its vec.iov_base, but auth->authorizer_buf still points at that freed memory. A subsequent msgr1 reconnect can therefore queue the stale pointer and trigger a KASAN slab-use-after-free in _copy_from_iter() while tcp_sendmsg() copies the authorizer. Refresh auth->authorizer_buf and auth->authorizer_buf_len after a successful authorizer rebuild so the messenger sends the current buffer.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 0bed9b5c523d577378b6f83eab5835fe30c27208 · fixed in 2334e9997308305ee4fd508fdfe6086c4150ed60; From 0bed9b5c523d577378b6f83eab5835fe30c27208 · fixed in 79a273df64238a4ade8b709689a78589f755b8ef; From 0bed9b5c523d577378b6f83eab5835fe30c27208 · fixed in 26f814187abceee90dbb29a02133adb4786fbb13; From 0bed9b5c523d577378b6f83eab5835fe30c27208 · fixed in 9d37aec9ffe4e743dabc3f84502e9723e17a30d4; From 0bed9b5c523d577378b6f83eab5835fe30c27208 · fixed in 75e82e8944ac1efe9fdb88bd2f14d9a031282bdf; From 0bed9b5c523d577378b6f83eab5835fe30c27208 · fixed in 0060ec912292a550198d8d18ac95b433c92a7091; From 0bed9b5c523d577378b6f83eab5835fe30c27208 · fixed in 5ecfcd5c05866f185357700b81b461dae4f5ebb2; From 0bed9b5c523d577378b6f83eab5835fe30c27208 · fixed in 937d61f86d377a3aa578adae7a3dfcecdddf9d89; From 3.4.50 · fixed in 3.5; From 3.9.7 · fixed in 3.10
- Linux Linux
3.10
- KernelLinux
From 3.10.0 · 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
References 8
git.kernel.org
- stable/c/2334e9997308305ee4fd508fdfe6086c4150ed60
- stable/c/79a273df64238a4ade8b709689a78589f755b8ef
- stable/c/26f814187abceee90dbb29a02133adb4786fbb13
- stable/c/9d37aec9ffe4e743dabc3f84502e9723e17a30d4
- stable/c/75e82e8944ac1efe9fdb88bd2f14d9a031282bdf
- stable/c/0060ec912292a550198d8d18ac95b433c92a7091
- stable/c/5ecfcd5c05866f185357700b81b461dae4f5ebb2
- stable/c/937d61f86d377a3aa578adae7a3dfcecdddf9d89