Missing Release of Resource after Effective Lifetime The advisory has been revoked - it doesn't affect any version of package libperf (opens in a new tab)
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-LIBPERF-15707912
- published20 Mar 2026
- disclosed18 Mar 2026
Introduced: 18 Mar 2026
CVE-2026-23261 (opens in a new tab)Amendment
The Red Hat security team deemed this advisory irrelevant for RHEL:10.
NVD Description
Note: Versions mentioned in the description apply only to the upstream libperf package and not the libperf package as distributed by RHEL.
In the Linux kernel, the following vulnerability has been resolved:
nvme-fc: release admin tagset if init fails
nvme_fabrics creates an NVMe/FC controller in following path:
nvmf_dev_write()
-> nvmf_create_ctrl()
-> nvme_fc_create_ctrl()
-> nvme_fc_init_ctrl()
nvme_fc_init_ctrl() allocates the admin blk-mq resources right after nvme_add_ctrl() succeeds. If any of the subsequent steps fail (changing the controller state, scheduling connect work, etc.), we jump to the fail_ctrl path, which tears down the controller references but never frees the admin queue/tag set. The leaked blk-mq allocations match the kmemleak report seen during blktests nvme/fc.
Check ctrl->ctrl.admin_tagset in the fail_ctrl path and call nvme_remove_admin_tag_set() when it is set so that all admin queue allocations are reclaimed whenever controller setup aborts.
References
- https://bugzilla.redhat.com/show_bug.cgi?id=2448686
- https://access.redhat.com/security/cve/CVE-2026-23261
- https://git.kernel.org/stable/c/b134dead095bc5a58fa2b98b90ae93428cb4b328
- https://git.kernel.org/stable/c/7c54d3f5ebbc5982daaa004260242dc07ac943ea
- https://git.kernel.org/stable/c/d1877cc7270302081a315a81a0ee8331f19f95c8
- https://git.kernel.org/stable/c/e810b290922c535feb34bc90ab549446fe94d2a3
- https://git.kernel.org/stable/c/fa301aef50e3f3b5be6ee53457608beae5aa7a01