CVE-2026-46024: Linux kernel · libceph: Prevent potential null-ptr-deref in ceph_handle_auth_reply()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in f101271fcf55d7eacfefd610b51ec65f46ba8118 : patch Linux kernel soon.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in f101271fcf55d7eacfefd610b51ec65f46ba8118, 5199c125d25aeae8615c4fc31652cc0fe624338e, 927e4bd5692f2a4901808822981fb2c8d4456548 +4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
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.
References
- git.kernel.org/stable/c/9ded62c302c0342efdb5eda3bf6e75720caad0df (opens in a new tab)
- git.kernel.org/stable/c/f101271fcf55d7eacfefd610b51ec65f46ba8118 (opens in a new tab)
- git.kernel.org/stable/c/4b2738b93edad661178340239de657d876b73d3d (opens in a new tab)
- git.kernel.org/stable/c/927e4bd5692f2a4901808822981fb2c8d4456548 (opens in a new tab)
- git.kernel.org/stable/c/016bc663657366d386993f63eb31072eb45a2b77 (opens in a new tab)
- git.kernel.org/stable/c/8f2be7285941a33a9f72579a23b96392f83c758e (opens in a new tab)
- git.kernel.org/stable/c/5199c125d25aeae8615c4fc31652cc0fe624338e (opens in a new tab)