CVE-2024-36908blk-iocost: do not WARN if iocg was already offlined
- 7.1HighCVSS base score
- 0.25%Exploitation in 30 daysEPSS · top 84% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: blk-iocost: do not WARN if iocg was already offlined In iocg_pay_debt(), warn is triggered if 'active_list' is empty, which is intended to confirm iocg is active when it has debt. However, warn can be triggered during a blkcg or disk removal, if iocg_waitq_timer_fn() is run at that time: WARNING: CPU: 0 PID: 2344971 at block/blk-iocost.c:1402 iocg_pay_debt+0x14c/0x190 Call trace: iocg_pay_debt+0x14c/0x190 iocg_kick_waitq+0x438/0x4c0 iocg_waitq_timer_fn+0xd8/0x130 __run_hrtimer+0x144/0x45c __hrtimer_run_queues+0x16c/0x244 hrtimer_interrupt+0x2cc/0x7b0 The warn in this situation is meaningless. Since this iocg is being removed, the state of the 'active_list' is irrelevant, and 'waitq_timer' is canceled after removing 'active_list' in ioc_pd_free(), which ensures iocg is freed after iocg_waitq_timer_fn() returns. Therefore, add the check if iocg was already offlined to avoid warn when removing a blkcg or disk.
Timeline
ID reserved
By Linux
Published
- 24 months later
· 24 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.25% · top 84% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.
Affected products
- affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < 56a9d07f427378eeb75b917bb49c6fbea8204126
- affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < 7d215e013d097ed6fc4b0ad0272c9514214dc408
- affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < aed0aac18f039dd4af13c143063754efca358cb0
- affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < 1c172ac7afe4442964f4153b2c78fe4e005d9d67
- affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < 14b3275f93d4a0d8ddc02195bc4e9869b7a3700e
- affected 7caa47151ab2e644dd221f741ec7578d9532c9a3 – < 01bc4fda9ea0a6b52f12326486f07a4910666cf6
- affected 5.4
- unaffected < 5.4
- unaffected 5.10.237 – ≤ 5.10.*
- unaffected 5.15.181 – ≤ 5.15.*
- unaffected 6.1.135 – ≤ 6.1.*
- unaffected 6.6.31 – ≤ 6.6.*
- unaffected 6.8.10 – ≤ 6.8.*
- unaffected 6.9 – ≤ *
References
References8
- https://git.kernel.org/stable/c/56a9d07f427378eeb75b917bb49c6fbea8204126 (opens in a new tab)
- https://git.kernel.org/stable/c/7d215e013d097ed6fc4b0ad0272c9514214dc408 (opens in a new tab)
- https://git.kernel.org/stable/c/aed0aac18f039dd4af13c143063754efca358cb0 (opens in a new tab)
- https://git.kernel.org/stable/c/1c172ac7afe4442964f4153b2c78fe4e005d9d67 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/14b3275f93d4a0d8ddc02195bc4e9869b7a3700e (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/01bc4fda9ea0a6b52f12326486f07a4910666cf6 (opens in a new tab)x_transferred
- https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-36259 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-36908)Record last updated .