VulnerabilityPublished 14 Feb 2026Updated 19 Oct 2026

CVE-2026-23136: Linux kernel · libceph: reset sparse-read state in osd_fault()

Affects Linux kernelSource CVE Database V5

Not known to be exploited · CVSS 7.5 High · fixed in e94075e950a6598e710b9f7dffea5aa388f40313 : patch Linux kernel soon.

Data as of 26 Oct 2026, 11:20 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS

0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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 e94075e950a6598e710b9f7dffea5aa388f40313, 11194b416ef95012c2cfe5f546d71af07b639e93, 90a60fe61908afa0eaf7f8fcf1421b9b50e5f7ff +1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Feb 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to e94075e950a6598e710b9f7dffea5aa388f40313, 11194b416ef95012c2cfe5f546d71af07b639e93, 90a60fe61908afa0eaf7f8fcf1421b9b50e5f7ff or 10b7c72810364226f7b27916ea3e2a4f870bc04b.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ f628d799972799023d32c2542bb2639eb8c4f84e, < e94075e950a6598e710b9f7dffea5aa388f40313	Fixed in e94075e950a6598e710b9f7dffea5aa388f40313
LinuxLinux	Affected ≥ f628d799972799023d32c2542bb2639eb8c4f84e, < 11194b416ef95012c2cfe5f546d71af07b639e93	Fixed in 11194b416ef95012c2cfe5f546d71af07b639e93
LinuxLinux	Affected ≥ f628d799972799023d32c2542bb2639eb8c4f84e, < 90a60fe61908afa0eaf7f8fcf1421b9b50e5f7ff	Fixed in 90a60fe61908afa0eaf7f8fcf1421b9b50e5f7ff
LinuxLinux	Affected ≥ f628d799972799023d32c2542bb2639eb8c4f84e, < 10b7c72810364226f7b27916ea3e2a4f870bc04b	Fixed in 10b7c72810364226f7b27916ea3e2a4f870bc04b
LinuxLinux	Affected =6.6	Fixed in–

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.

CWE-667Improper Locking (opens in a new tab)
Class weakness
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
Implementation · Libraries or Frameworks
Use industry standard APIs to implement locking mechanism.
Attack patterns
Leveraging Race Conditions via Symbolic Links (opens in a new tab)
Forced Deadlock (opens in a new tab)
Leveraging Race Conditions (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

WeaknessesCWE-667

Technical details

References

Community reviews

Related threats