CVE-2025-39999
Last modified
CVE-2025-39999 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: blk-mq: fix blk_mq_tags double free while nr_requests grown In the case user trigger tags grow by queue sysfs attribute nr_requests, hctx->sched_tags will be freed directly and replaced with a new allocated tags, see blk_mq_tag_update_depth(). The problem is that hctx->sched_tags is from elevator->et->tags, while et->tags is still the freed tags, hence later elevator exit will try to free the tags again, causing kernel panic. Fix this problem by replacing et->tags with new allocated tags as well. Noted there are still some long term problems that will require some refactor to be fixed thoroughly[1]. [1] https://lore.kernel.org/all/20250815080216.410665-1-yukuai1@huaweicloud.com/. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: blk-mq: fix blk_mq_tags double free while nr_requests grown In the case user trigger tags grow by queue sysfs attribute nr_requests, hctx->sched_tags will be freed directly and replaced with a new allocated tags, see blk_mq_tag_update_depth(). The problem is that hctx->sched_tags is from elevator->et->tags, while et->tags is still the freed tags, hence later elevator exit will try to free the tags again, causing kernel panic. Fix this problem by replacing et->tags with new allocated tags as well. Noted there are still some long term problems that will require some refactor to be fixed thoroughly[1]. [1] https://lore.kernel.org/all/20250815080216.410665-1-yukuai1@huaweicloud.com/
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 58567d8e95c096ad234963df90a2ca518901f4b6, < 8faee580d63bc2a54a59dcdb7f9ce4de29384fec; >= f5a6604f7a4405450e4a1f54e5430f47290c500f, < 392b1d64911f4de8887fe8b68299fa8bd6e5b923; >= f5a6604f7a4405450e4a1f54e5430f47290c500f, < ba28afbd9eff2a6370f23ef4e6a036ab0cfda409; >= 6.16.4, < 6.16.11 |
| Linux | Linux | 6.17 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-39999?
How severe is CVE-2025-39999?
How do I fix CVE-2025-39999?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-39993In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-39994In the Linux kernel, the following vulnerability has been re…7.3
- CVE-2025-39995In the Linux kernel, the following vulnerability has been re…
- CVE-2025-39996In the Linux kernel, the following vulnerability has been re…
- CVE-2025-39997In the Linux kernel, the following vulnerability has been re…
- CVE-2025-39998In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-4000A vulnerability, which was classified as problematic, was fo…5.4
- CVE-2025-40000In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2025-40001In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40002In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40003In the Linux kernel, the following vulnerability has been re…
- CVE-2025-40004In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2025-39999?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
