CVE-2026-68157: Linux kernel · libceph: guard missing CRUSH type name lookup
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in db9cc9fd9660b2d69ee66f5a4cbec83c21a1c64d : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 52% 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 db9cc9fd9660b2d69ee66f5a4cbec83c21a1c64d, cbfcba275326c8c7dae9acd8f4a0d4c316fdafb0, c46d82c47afc968d6ee8ef4470fa2dd35b765c21 +5
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 10 Aug 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: guard missing CRUSH type name lookup Localized read selection can walk a parent bucket whose name exists in the CRUSH map while its type has no matching entry in type_names. get_immediate_parent() then dereferences a NULL type_cn and passes an invalid pointer into strcmp(), causing a null-ptr-deref. Skip such malformed parent buckets unless both the bucket name and type name metadata are present. This keeps malformed hierarchy data from crashing locality lookup and safely falls back to "not local". [ idryomov: add WARN_ON_ONCE ]
References
- git.kernel.org/stable/c/cbfcba275326c8c7dae9acd8f4a0d4c316fdafb0 (opens in a new tab)
- git.kernel.org/stable/c/8ff579ac03d6e9d17d6d9c8443110167c14a382d (opens in a new tab)
- git.kernel.org/stable/c/6a4b75d90f0cfbf22c14742ab35a803bc13f36ec (opens in a new tab)
- git.kernel.org/stable/c/c46d82c47afc968d6ee8ef4470fa2dd35b765c21 (opens in a new tab)
- git.kernel.org/stable/c/3767c9f0c1bbd98dd25cb088356a0fc6c1f09f50 (opens in a new tab)
- git.kernel.org/stable/c/4716a64b7cc2797741f7be4e283ace78a9dff37d (opens in a new tab)
- git.kernel.org/stable/c/db9cc9fd9660b2d69ee66f5a4cbec83c21a1c64d (opens in a new tab)
- git.kernel.org/stable/c/bbeae12fda3384a90fbebc8a19ba9d33f85b5361 (opens in a new tab)