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.
Metrics
Affected Vendors & Products
Source | ID | Title |
---|---|---|
![]() |
DLA-4178-1 | linux security update |
![]() |
DLA-4193-1 | linux-6.1 security update |
![]() |
DSA-5907-1 | linux security update |
![]() |
EUVD-2024-36259 | 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. |
![]() |
USN-6949-1 | Linux kernel vulnerabilities |
![]() |
USN-6949-2 | Linux kernel vulnerabilities |
![]() |
USN-6952-1 | Linux kernel vulnerabilities |
![]() |
USN-6955-1 | Linux kernel (OEM) vulnerabilities |
![]() |
USN-7654-1 | Linux kernel vulnerabilities |
![]() |
USN-7654-2 | Linux kernel (Real-time) vulnerabilities |
![]() |
USN-7654-3 | Linux kernel (FIPS) vulnerabilities |
![]() |
USN-7654-4 | Linux kernel (KVM) vulnerabilities |
![]() |
USN-7654-5 | Linux kernel (Xilinx ZynqMP) vulnerabilities |
![]() |
USN-7655-1 | Linux kernel (Intel IoTG) vulnerabilities |
![]() |
USN-7686-1 | Linux kernel (Raspberry Pi) vulnerabilities |
![]() |
USN-7711-1 | Linux kernel (Azure) vulnerabilities |
![]() |
USN-7712-1 | Linux kernel (Azure FIPS) vulnerabilities |
![]() |
USN-7712-2 | Linux kernel (Azure) vulnerabilities |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 30 Sep 2025 18:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | NVD-CWE-noinfo | |
CPEs | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.9:rc1:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.9:rc2:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.9:rc3:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.9:rc4:*:*:*:*:*:* |
Wed, 16 Jul 2025 13:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
epss
|
epss
|
Sat, 12 Jul 2025 13:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
epss
|
epss
|
Fri, 02 May 2025 06:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
|
Fri, 25 Apr 2025 10:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
|
Thu, 07 Nov 2024 17:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
cvssV3_1
|
cvssV3_1
|
Wed, 06 Nov 2024 20:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|

Status: PUBLISHED
Assigner: Linux
Published:
Updated: 2025-05-04T09:11:51.263Z
Reserved: 2024-05-30T15:25:07.067Z
Link: CVE-2024-36908

Updated: 2024-08-02T03:43:49.881Z

Status : Analyzed
Published: 2024-05-30T16:15:14.300
Modified: 2025-09-30T17:51:14.207
Link: CVE-2024-36908


Updated: 2025-07-12T22:31:42Z