libceph: Prevent potential null-ptr-deref in ceph_handle_auth_reply()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4e7a5dcd1bbab6560fbc8ada29a840e7a20ed7bc · < 8f2be7285941a33a9f72579a23b96392f83c758e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
libceph: Prevent potential null-ptr-deref in ceph_handle_auth_reply()
If a message of type CEPH_MSG_AUTH_REPLY contains a zero value for both protocol and result, this is currently not treated as an error. In case of ac->negotiating == true and ac->protocol > 0, this leads to setting ac->protocol = 0 and ac->ops = NULL. Thereafter, the check for ac->protocol != protocol returns false, and init_protocol() is not called. Subsequently, ac->ops->handle_reply() is called, which leads to a null pointer dereference, because ac->ops is still NULL.
This patch changes the check for ac->protocol != protocol to !ac->protocol, as this also includes the case when the protocol was set to zero in the message. This causes the message to be treated as containing a bad auth protocol.
From the CVE record · Linux
The Linux kernel's libceph authentication reply handler can dereference a null pointer when an auth reply contains zero for both protocol and result while authentication is being negotiated and the existing protocol is nonzero. Such a reply can trigger the dereference; the input does not establish whether an attacker can send it, or specify authentication or user-interaction requirements.
Engineers running Linux kernels that include libceph should check whether their kernel contains the fix; affected versions were not specified.