# CVE-2026-68157: libceph: guard missing CRUSH type name lookup

> A null pointer dereference in the Linux kernel's libceph module allows attackers to cause a denial of service via malformed CRUSH map data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-68157, DEBIAN-CVE-2026-68157, GHSA-mr29-956m-24vp, UBUNTU-CVE-2026-68157

## What is CVE-2026-68157?

CVE-2026-68157 is a high-severity vulnerability in Linux, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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 ]

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-68157?


## How do I fix CVE-2026-68157?

Apply the vendor's patch.

## Is CVE-2026-68157 being exploited?

There is no known exploitation of CVE-2026-68157 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68157 and fix it if it is affected.

What it is: CVE-2026-68157 is a high-severity vulnerability in Linux, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68157 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68157/ (Markdown: https://insights.sbomify.com/CVE-2026-68157/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68157
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68157
- OSV: https://osv.dev/vulnerability/CVE-2026-68157

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68157/
Summaries are generated and may contain mistakes; the official description above is the record.