# CVE-2026-23136: libceph: reset sparse-read state in osd_fault()

> A failure to reset sparse-read state in the Linux kernel Ceph client can cause infinite loops and socket errors, leading to denial of service.

- **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:** 14 Feb 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-23136, DEBIAN-CVE-2026-23136, GHSA-v844-6465-jhqh, ROOT-OS-UBUNTU-2404-CVE-2026-23136, UBUNTU-CVE-2026-23136

## What is CVE-2026-23136?

CVE-2026-23136 is a high-severity denial of service vulnerability in Linux kernel, published on 14 Feb 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: reset sparse-read state in osd_fault()

When a fault occurs, the connection is abandoned, reestablished, and any
pending operations are retried. The OSD client tracks the progress of a
sparse-read reply using a separate state machine, largely independent of
the messenger's state.

If a connection is lost mid-payload or the sparse-read state machine
returns an error, the sparse-read state is not reset. The OSD client
will then interpret the beginning of a new reply as the continuation of
the old one. If this makes the sparse-read machinery enter a failure
state, it may never recover, producing loops like:

  libceph:  [0] got 0 extents
  libceph: data len 142248331 != extent len 0
  libceph: osd0 (1)...:6801 socket error on read
  libceph: data len 142248331 != extent len 0
  libceph: osd0 (1)...:6801 socket error on read

Therefore, reset the sparse-read state in osd_fault(), ensuring retries
start from a clean state.

Weakness: CWE-667 (Improper Locking)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-23136 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-23136 is a high-severity denial of service vulnerability in Linux kernel, published on 14 Feb 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-23136 in the wild and no public exploit code.

Affected product: Linux kernel. 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-23136/ (Markdown: https://insights.sbomify.com/CVE-2026-23136/index.md)
```

## Sources

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

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