Skip to content
Noroxi
CVE-2026-23136· NVD / CVE Program· CNA Linux

libceph: reset sparse-read state in osd_fault()

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.32% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 10b7c72810364226f7b27916ea3e2a4f870bc04b, 11194b416ef95012c2cfe5f546d71af07b639e93, 90a60fe61908afa0eaf7f8fcf1421b9b50e5f7ff.
  • Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 10b7c72810364226f7b27916ea3e2a4f870bc04b, 11194b416ef95012c2cfe5f546d71af07b639e93, 90a60fe61908afa0eaf7f8fcf1421b9b50e5f7ff or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Feb 14, 2026
Updated
Oct 16, 2026
EPSS
0.3% · 24th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.5
2.0 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-23136

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.6 and later · before 6.6.121
  • linux linux kernel6.7 and later · before 6.12.66
  • linux linux kernel6.13 and later · before 6.18.6
  • linux linux kernel6.19

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.6affected
    • f628d799972799023d32c2542bb2639eb8c4f84e and later · before 90a60fe61908afa0eaf7f8fcf1421b9b50e5f7ffaffected · git
    • f628d799972799023d32c2542bb2639eb8c4f84e and later · before e94075e950a6598e710b9f7dffea5aa388f40313affected · git
    • f628d799972799023d32c2542bb2639eb8c4f84e and later · before 10b7c72810364226f7b27916ea3e2a4f870bc04baffected · git
    • f628d799972799023d32c2542bb2639eb8c4f84e and later · before 11194b416ef95012c2cfe5f546d71af07b639e93affected · git
    • before 6.6not affected · semver
    • 6.6.121 and later · up to and including 6.6.*not affected · semver
    • 6.12.66 and later · up to and including 6.12.*not affected · semver
    • 6.18.6 and later · up to and including 6.18.*not affected · semver
    • 6.19 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.60.1.el10_26.12.0-211.60.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-23113Feb 14, 2026 · io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop
    22Monitor
  • ← EarlierCVE-2025-71202Feb 14, 2026 · iommu/sva: invalidate stale IOTLB entries for kernel address space
    22Monitor
  • Later →CVE-2026-23141Feb 14, 2026 · btrfs: send: check for inline extents in range_is_hole_in_parent()
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux10b7c72810364226f7b27916ea3e2a4f870bc04bVendor (CNA)
Linux Linux11194b416ef95012c2cfe5f546d71af07b639e93Vendor (CNA)
Linux Linux90a60fe61908afa0eaf7f8fcf1421b9b50e5f7ffVendor (CNA)
Linux Linuxe94075e950a6598e710b9f7dffea5aa388f40313Vendor (CNA)
almalinux:kernel5.14.0-611.54.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-611.54.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-611.54.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-611.54.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-611.54.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-611.54.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-611.54.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-611.54.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-611.54.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-611.54.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-611.54.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-611.54.1.el9_7 · AlmaLinux:9Package registry (OSV)
debian:linux6.12.69-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-611.54.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-611.54.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-611.54.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-611.54.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-611.54.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-611.54.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-611.54.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-611.54.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-611.54.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-611.54.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-611.54.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-611.54.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:kernel0:5.14.0-611.54.1.el9_7 · Rocky Linux:9Package registry (OSV)

+8

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records