Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 22 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 922dab6134178cae317ae00de86376cba59f3147 – < 2b3329b3c29d9e188e40d902d5230c2d5989b940
    • affected 922dab6134178cae317ae00de86376cba59f3147 – < 5d0dc83cb9a69c1d0bea58f1c430199b05f6b021
    • affected 922dab6134178cae317ae00de86376cba59f3147 – < 4d3399c52e0e61720ae898f5a0b5b75d4460ae24
    • affected 922dab6134178cae317ae00de86376cba59f3147 – < 4ebc711b738d139cabe2fc9e7e7749847676a342
    • affected 922dab6134178cae317ae00de86376cba59f3147 – < 6f468f6ff233c6a81e0e761d9124e982903fe9a5
    • affected 922dab6134178cae317ae00de86376cba59f3147 – < 5647d42c47b535573b63e073e91164d6a5bb058c
    • affected 922dab6134178cae317ae00de86376cba59f3147 – < c0fe2994f9a9d0a2ec9e42441ea5ba74b6a16176
  • Linux · Linux

    • affected 4.7
    • unaffected < 4.7
    • unaffected 5.10.248 – ≤ 5.10.*
    • unaffected 5.15.198 – ≤ 5.15.*
    • unaffected 6.1.161 – ≤ 6.1.*
    • unaffected 6.6.121 – ≤ 6.6.*
    • unaffected 6.12.66 – ≤ 6.12.*
    • unaffected 6.18.6 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23047 badge
[![CVE-2026-23047](https://cveledger.app/badge/CVE-2026-23047.svg)](https://cveledger.app/cve/CVE-2026-23047)

Record last updated .