Deadlock Affecting kernel-devel-matched package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RHEL10-KERNELDEVELMATCHED-15212656
- published5 Feb 2026
- disclosed4 Feb 2026
Introduced: 4 Feb 2026
NewCVE-2026-23047 (opens in a new tab)How to fix?
There is no fixed version for RHEL:10 kernel-devel-matched.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-devel-matched package and not the kernel-devel-matched package as distributed by RHEL.
See How to fix? for RHEL:10 relevant fixed versions and status.
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.
References
- https://bugzilla.redhat.com/show_bug.cgi?id=2436815
- https://access.redhat.com/security/cve/CVE-2026-23047
- https://git.kernel.org/stable/c/2b3329b3c29d9e188e40d902d5230c2d5989b940
- https://git.kernel.org/stable/c/4d3399c52e0e61720ae898f5a0b5b75d4460ae24
- https://git.kernel.org/stable/c/4ebc711b738d139cabe2fc9e7e7749847676a342
- https://git.kernel.org/stable/c/5647d42c47b535573b63e073e91164d6a5bb058c
- https://git.kernel.org/stable/c/5d0dc83cb9a69c1d0bea58f1c430199b05f6b021
- https://git.kernel.org/stable/c/6f468f6ff233c6a81e0e761d9124e982903fe9a5
- https://git.kernel.org/stable/c/c0fe2994f9a9d0a2ec9e42441ea5ba74b6a16176