libceph: Fix slab-out-of-bounds access in auth message processing
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel 1c439de70b1c3eb3c6bffa8245c16b9fc318f114, Kernel 2ae0afd98432536562fa8261538ae795446f0589, Kernel 38fdf04c602d52c42c67fc1617211492753b7e8b and 4 more.
In the Linux kernel, the following vulnerability has been resolved: libceph: Fix slab-out-of-bounds access in auth message processing If a (potentially corrupted) message of type CEPH_MSG_AUTH_REPLY contains a positive value in its result field, it is treated as an error code by ceph_handle_auth_reply() and returned to handle_auth_reply(). Thereafter, an attempt is made to send the preallocated message of type CEPH_MSG_AUTH, where the returned value is interpreted as the size of the front segment to send. If the result value in the message is greater than the size of the memory buffer allocated for the front segment, an out-of-bounds access occurs, and the content of the memory region beyond this buffer is sent out. This patch fixes the issue by treating only negative values in the result field as errors. Positive values are therefore treated as success in the same way as a zero value. Additionally, a BUG_ON is added to __send_prepared_auth_request() comparing the len parameter to front_alloc_len to prevent sending the message if it exceeds the bounds of the allocation and to make it easier to catch any logic flaws leading to this.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.34, >=4e7a5dcd1bbab6560fbc8ada29a840e7a20ed7bc <1c439de70b1c3eb3c6bffa8245c16b9fc318f114, >=4e7a5dcd1bbab6560fbc8ada29a840e7a20ed7bc <2ae0afd98432536562fa8261538ae795446f0589, >=4e7a5dcd1bbab6560fbc8ada29a840e7a20ed7bc <38fdf04c602d52c42c67fc1617211492753b7e8b, >=4e7a5dcd1bbab6560fbc8ada29a840e7a20ed7bc <408e85ee708b6aa03eeb0220ffa0915f4d407181, >=4e7a5dcd1bbab6560fbc8ada29a840e7a20ed7bc <8517b6c8d2c759918ba0058cb6c7e14d59643202, >=4e7a5dcd1bbab6560fbc8ada29a840e7a20ed7bc <b7df9fbd4869fdfe09a3f501ffd228486521e062, >=4e7a5dcd1bbab6560fbc8ada29a840e7a20ed7bc <c2374b92c729d0388a538b3cde7b3e3b5e55ef39 | 1c439de70b1c3eb3c6bffa8245c16b9fc318f114, 2ae0afd98432536562fa8261538ae795446f0589, 38fdf04c602d52c42c67fc1617211492753b7e8b, 408e85ee708b6aa03eeb0220ffa0915f4d407181, 8517b6c8d2c759918ba0058cb6c7e14d59643202, b7df9fbd4869fdfe09a3f501ffd228486521e062, c2374b92c729d0388a538b3cde7b3e3b5e55ef39 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket