libceph: fix invalid accesses to ceph_connection_v1_info
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ cd1a677cad994021b19665ed476aea63f5d54f31 · < cdbc9836c7afadad68f374791738f118263c5371| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
libceph: fix invalid accesses to ceph_connection_v1_info
There is a place where generic code in messenger.c is reading and another place where it is writing to con->v1 union member without checking that the union member is active (i.e. msgr1 is in use).
On 64-bit systems, con->v1.auth_retry overlaps with con->v2.out_iter, so such a read is almost guaranteed to return a bogus value instead of 0 when msgr2 is in use. This ends up being fairly benign because the side effect is just the invalidation of the authorizer and successive fetching of new tickets.
con->v1.connect_seq overlaps with con->v2.conn_bufs and the fact that it's being written to can cause more serious consequences, but luckily it's not something that happens often.
From the CVE record · Linux
The Linux kernel’s libceph messenger can read or write a v1 connection field while msgr2 is in use. A read can trigger unnecessary ticket fetching, while a less frequent write can have more serious consequences. The input does not describe an attacker path or specify whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with libceph should check their deployments; affected versions are not specified.