Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-23047: libceph: make calc_target() set t->paused, not just clear it

Noroxi assessment

Priority: Monitor (action score 0/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.19% (FIRST EPSS).
  • Fixed version: Linux Linux 2b3329b3c29d9e188e40d902d5230c2d5989b940, 4d3399c52e0e61720ae898f5a0b5b75d4460ae24, 4ebc711b738d139cabe2fc9e7e7749847676a342.

Low priority for now. Upgrade to Linux Linux 2b3329b3c29d9e188e40d902d5230c2d5989b940, 4d3399c52e0e61720ae898f5a0b5b75d4460ae24, 4ebc711b738d139cabe2fc9e7e7749847676a342 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: make calc_target() set t->paused, not just clear it Currently calc_target() clears t->paused if the request shouldn't be paused anymore, but doesn't ever set t->paused even though it's able to determine when the request should be paused. Setting t->paused is left to __submit_request() which is fine for regular requests but doesn't work for linger requests -- since __submit_request() doesn't operate on linger requests, there is nowhere for lreq->t.paused to be set. One consequence of this is that watches don't get reestablished on paused -> unpaused transitions in cases where requests have been paused long enough for the (paused) unwatch request to time out and for the subsequent (re)watch request to enter the paused state. On top of the watch not getting reestablished, rbd_reregister_watch() gets stuck with rbd_dev->watch_mutex held: rbd_register_watch __rbd_register_watch ceph_osdc_watch linger_reg_commit_wait It's waiting for lreq->reg_commit_wait to be completed, but for that to happen the respective request needs to end up on need_resend_linger list and be kicked when requests are unpaused. There is no chance for that if the request in question is never marked paused in the first place. The fact that rbd_dev->watch_mutex remains taken out forever then prevents the image from getting unmapped -- "rbd unmap" would inevitably hang in D state on an attempt to grab the mutex.

—No exploit Fix available
Published
Feb 4, 2026
Updated
Jun 17, 2026
EPSS
0.1% · 9th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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-23047

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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.

—

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

    • 4.7affected
    • 922dab6134178cae317ae00de86376cba59f3147 and later · before 2b3329b3c29d9e188e40d902d5230c2d5989b940affected · git
    • 922dab6134178cae317ae00de86376cba59f3147 and later · before 5d0dc83cb9a69c1d0bea58f1c430199b05f6b021affected · git
    • 922dab6134178cae317ae00de86376cba59f3147 and later · before 4d3399c52e0e61720ae898f5a0b5b75d4460ae24affected · git
    • 922dab6134178cae317ae00de86376cba59f3147 and later · before 4ebc711b738d139cabe2fc9e7e7749847676a342affected · git
    • 922dab6134178cae317ae00de86376cba59f3147 and later · before 6f468f6ff233c6a81e0e761d9124e982903fe9a5affected · git
    • 922dab6134178cae317ae00de86376cba59f3147 and later · before 5647d42c47b535573b63e073e91164d6a5bb058caffected · git
    • 922dab6134178cae317ae00de86376cba59f3147 and later · before c0fe2994f9a9d0a2ec9e42441ea5ba74b6a16176affected · git
    • before 4.7not affected · semver
    • 5.10.248 and later · up to and including 5.10.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.18.8-16.18.8-1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_11before 1-150700.1.3.11-150700.1.3.1
SUSE:Linux Micro 6.1kernel-defaultbefore 6.4.0-41.16.4.0-41.1
SUSE:Linux Micro 6.1kernel-default-basebefore 6.4.0-41.1.21.186.4.0-41.1.21.18
SUSE:Linux Micro 6.1kernel-kvmsmallbefore 6.4.0-41.16.4.0-41.1
SUSE:Linux Micro 6.1kernel-rtbefore 6.4.0-41.16.4.0-41.1
SUSE:Linux Micro 6.1kernel-sourcebefore 6.4.0-41.16.4.0-41.1
SUSE:Linux Micro 6.1kernel-source-rtbefore 6.4.0-41.16.4.0-41.1
SUSE:Real Time Module 15 SP7kernel-rtbefore 6.4.0-150700.7.37.26.4.0-150700.7.37.2
SUSE:Real Time Module 15 SP7kernel-source-rtbefore 6.4.0-150700.7.37.26.4.0-150700.7.37.2
SUSE:Real Time Module 15 SP7kernel-syms-rtbefore 6.4.0-150700.7.37.16.4.0-150700.7.37.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-23045Feb 4, 2026 · net/ena: fix missing lock when update devlink params
    0Monitor
  • ← EarlierCVE-2026-23046Feb 4, 2026 · virtio_net: fix device mismatch in devm_kzalloc/devm_kfree
    0Monitor
  • Later →CVE-2026-23048Feb 4, 2026 · udp: call skb_orphan() before skb_attempt_defer_free()
    0Monitor

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 Linux2b3329b3c29d9e188e40d902d5230c2d5989b940Vendor (CNA)
Linux Linux4d3399c52e0e61720ae898f5a0b5b75d4460ae24Vendor (CNA)
Linux Linux4ebc711b738d139cabe2fc9e7e7749847676a342Vendor (CNA)
Linux Linux5647d42c47b535573b63e073e91164d6a5bb058cVendor (CNA)
Linux Linux5d0dc83cb9a69c1d0bea58f1c430199b05f6b021Vendor (CNA)
Linux Linux6f468f6ff233c6a81e0e761d9124e982903fe9a5Vendor (CNA)
Linux Linuxc0fe2994f9a9d0a2ec9e42441ea5ba74b6a16176Vendor (CNA)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
suse:kernel-default6.4.0-41.1 · SUSE:Linux Micro 6.1Package registry (OSV)
suse:kernel-default-base6.4.0-41.1.21.18 · SUSE:Linux Micro 6.1Package registry (OSV)
suse:kernel-kvmsmall6.4.0-41.1 · SUSE:Linux Micro 6.1Package registry (OSV)
suse:kernel-livepatch-SLE15-SP7-RT_Update_111-150700.1.3.1 · SUSE:Linux Enterprise Live Patching 15 SP7Package registry (OSV)
suse:kernel-rt6.4.0-150700.7.37.2 · SUSE:Real Time Module 15 SP7Package registry (OSV)
suse:kernel-source6.4.0-41.1 · SUSE:Linux Micro 6.1Package registry (OSV)
suse:kernel-source-rt6.4.0-150700.7.37.2 · SUSE:Real Time Module 15 SP7Package registry (OSV)
suse:kernel-syms-rt6.4.0-150700.7.37.1 · SUSE:Real Time Module 15 SP7Package registry (OSV)

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.

No history yet (it accumulates with the daily EPSS job).

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.

Credits

All researchers

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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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. Fix✗ → ✓

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

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records