UBUNTU-CVE-2024-50249
In the Linux kernel, the following vulnerability has been resolved: ACPI: CPPC: Make rmw_lock a raw_spin_lock The following BUG was triggered: ============================= [ BUG: Invalid wait context ] 6.12.0-rc2-XXX #406 Not tainted ----------------------------- kworker/1:1/62 is trying to lock: ffffff8801593030 (&cpc_ptr->rmw_lock){+.+.}-{3:3}, at: cpc_write+0xcc/0x370 other info that might help us debug this: context-{5:5} 2 locks held by kworker/1:1/62: #0: ffffff897ef5ec98 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2c/0x50 #1: ffffff880154e238 (&sg_policy->update_lock){....}-{2:2}, at: sugov_update_shared+0x3c/0x280 stack backtrace: CPU: 1 UID: 0 PID: 62 Comm: kworker/1:1 Not tainted 6.12.0-rc2-g9654bd3e8806 #406 Workqueue: 0x0 (events) Call trace: dump_backtrace+0xa4/0x130 show_stack+0x20/0x38 dump_stack_lvl+0x90/0xd0 dump_stack+0x18/0x28 __lock_acquire+0x480/0x1ad8 lock_acquire+0x114/0x310 _raw_spin_lock+0x50/0x70 cpc_write+0xcc/0x370 cppc_set_perf+0xa0/0x3a8 cppc_cpufreq_fast_switch+0x40/0xc0 cpufreq_driver_fast_switch+0x4c/0x218 sugov_update_shared+0x234/0x280 update_load_avg+0x6ec/0x7b8 dequeue_entities+0x108/0x830 dequeue_task_fair+0x58/0x408 __schedule+0x4f0/0x1070 schedule+0x54/0x130 worker_thread+0xc0/0x2e8 kthread+0x130/0x148 ret_from_fork+0x10/0x20 sugov_update_shared() locks a raw_spinlock while cpc_write() locks a spinlock. To have a correct wait-type order, update rmw_lock to a raw spinlock and ensure that interrupts will be disabled on the CPU holding it. [ rjw: Changelog edits ]
02 / AFFECTED SOFTWARE
Affected packages
16 explicit affected versions
2 explicit affected versions
59 explicit affected versions
14 explicit affected versions
51 explicit affected versions
29 explicit affected versions
10 explicit affected versions
11 explicit affected versions
15 explicit affected versions
1 explicit affected versions
41 explicit affected versions
53 explicit affected versions
18 explicit affected versions
7 explicit affected versions
26 explicit affected versions
37 explicit affected versions
15 explicit affected versions
10 explicit affected versions
52 explicit affected versions
10 explicit affected versions
13 explicit affected versions
19 explicit affected versions
13 explicit affected versions
17 explicit affected versions
11 explicit affected versions
78 explicit affected versions
45 explicit affected versions
37 explicit affected versions
8 explicit affected versions
4 explicit affected versions
60 explicit affected versions
63 explicit affected versions
8 explicit affected versions
19 explicit affected versions
23 explicit affected versions
7 explicit affected versions
14 explicit affected versions
10 explicit affected versions
16 explicit affected versions
33 explicit affected versions
16 explicit affected versions
13 explicit affected versions
12 explicit affected versions
38 explicit affected versions
51 explicit affected versions
13 explicit affected versions
10 explicit affected versions
10 explicit affected versions
58 explicit affected versions
13 explicit affected versions
10 explicit affected versions
10 explicit affected versions
50 explicit affected versions
1 explicit affected versions
20 explicit affected versions
8 explicit affected versions
13 explicit affected versions
21 explicit affected versions
59 explicit affected versions
6 explicit affected versions
13 explicit affected versions
12 explicit affected versions
24 explicit affected versions
20 explicit affected versions
7 explicit affected versions
14 explicit affected versions
60 explicit affected versions
20 explicit affected versions
34 explicit affected versions
12 explicit affected versions
26 explicit affected versions
41 explicit affected versions
60 explicit affected versions
67 explicit affected versions
16 explicit affected versions
23 explicit affected versions
13 explicit affected versions
14 explicit affected versions
57 explicit affected versions
5 explicit affected versions
44 explicit affected versions
33 explicit affected versions
52 explicit affected versions
51 explicit affected versions
18 explicit affected versions
34 explicit affected versions
3 explicit affected versions
23 explicit affected versions
26 explicit affected versions
21 explicit affected versions
19 explicit affected versions
12 explicit affected versions
44 explicit affected versions
21 explicit affected versions
4 explicit affected versions
4 explicit affected versions
22 explicit affected versions
16 explicit affected versions
12 explicit affected versions
9 explicit affected versions
12 explicit affected versions
52 explicit affected versions
19 explicit affected versions
13 explicit affected versions
26 explicit affected versions
21 explicit affected versions
8 explicit affected versions
22 explicit affected versions
7 explicit affected versions
50 explicit affected versions
13 explicit affected versions
7 explicit affected versions
10 explicit affected versions
14 explicit affected versions
25 explicit affected versions
12 explicit affected versions
18 explicit affected versions
24 explicit affected versions
3 explicit affected versions
16 explicit affected versions
19 explicit affected versions
43 explicit affected versions
11 explicit affected versions
47 explicit affected versions
15 explicit affected versions
64 explicit affected versions
35 explicit affected versions
12 explicit affected versions
13 explicit affected versions
6 explicit affected versions
12 explicit affected versions
50 explicit affected versions
11 explicit affected versions
12 explicit affected versions
15 explicit affected versions
58 explicit affected versions
27 explicit affected versions
12 explicit affected versions
7 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
In the Linux kernel, the following vulnerability has been resolved: ACPI: CPPC: Make rmw_lock a raw_spin_lock The following BUG was triggered: ============================= [ BUG: Invalid wait context ] 6.12.0-rc2-XXX #406 Not tainted ----------------------------- kworker/1:1/62 is trying to lock: ffffff8801593030 (&cpc_ptr->rmw_lock){+.+.}-{3:3}, at: cpc_write+0xcc/0x370 other info that might help us debug this: context-{5:5} 2 locks held by kworker/1:1/62: #0: ffffff897ef5ec98 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x2c/0x50 #1: ffffff880154e238 (&sg_policy->update_lock){....}-{2:2}, at: sugov_update_shared+0x3c/0x280 stack backtrace: CPU: 1 UID: 0 PID: 62 Comm: kworker/1:1 Not tainted 6.12.0-rc2-g9654bd3e8806 #406 Workqueue: 0x0 (events) Call trace: dump_backtrace+0xa4/0x130 show_stack+0x20/0x38 dump_stack_lvl+0x90/0xd0 dump_stack+0x18/0x28 __lock_acquire+0x480/0x1ad8 lock_acquire+0x114/0x310 _raw_spin_lock+0x50/0x70 cpc_write+0xcc/0x370 cppc_set_perf+0xa0/0x3a8 cppc_cpufreq_fast_switch+0x40/0xc0 cpufreq_driver_fast_switch+0x4c/0x218 sugov_update_shared+0x234/0x280 update_load_avg+0x6ec/0x7b8 dequeue_entities+0x108/0x830 dequeue_task_fair+0x58/0x408 __schedule+0x4f0/0x1070 schedule+0x54/0x130 worker_thread+0xc0/0x2e8 kthread+0x130/0x148 ret_from_fork+0x10/0x20 sugov_update_shared() locks a raw_spinlock while cpc_write() locks a spinlock. To have a correct wait-type order, update rmw_lock to a raw spinlock and ensure that interrupts will be disabled on the CPU holding it. [ rjw: Changelog edits ]
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/1c10941e34c5fdc0357e46a25bd130d9cf40b925
- https://git.kernel.org/stable/c/0eb2b767c42fac61ab23c4063eb456baa4c2c262
- https://git.kernel.org/stable/c/1c10941e34c5fdc0357e46a25bd130d9cf40b925
- https://git.kernel.org/stable/c/23039b4aaf1e82e0feea1060834d4ec34262e453
- https://git.kernel.org/stable/c/43b1df48d1e7000a214acd1a81b8012ca8a929c8
- https://git.kernel.org/stable/c/c46d6b02588000c27b7b869388c2c0278bd0d173
- https://ubuntu.com/security/CVE-2024-50249
- https://ubuntu.com/security/notices/USN-7276-1
- https://ubuntu.com/security/notices/USN-7277-1
- https://ubuntu.com/security/notices/USN-7288-1
- https://ubuntu.com/security/notices/USN-7288-2
- https://ubuntu.com/security/notices/USN-7289-1
- https://ubuntu.com/security/notices/USN-7289-2
- https://ubuntu.com/security/notices/USN-7289-3
- https://ubuntu.com/security/notices/USN-7289-4
- https://ubuntu.com/security/notices/USN-7291-1
- https://ubuntu.com/security/notices/USN-7305-1
- https://ubuntu.com/security/notices/USN-7308-1
- https://ubuntu.com/security/notices/USN-7331-1
- https://ubuntu.com/security/notices/USN-7388-1
- https://ubuntu.com/security/notices/USN-7389-1
- https://ubuntu.com/security/notices/USN-7390-1
- https://ubuntu.com/security/notices/USN-7449-1
- https://ubuntu.com/security/notices/USN-7449-2
- https://ubuntu.com/security/notices/USN-7450-1
- https://ubuntu.com/security/notices/USN-7451-1
- https://ubuntu.com/security/notices/USN-7452-1
- https://ubuntu.com/security/notices/USN-7453-1
- https://ubuntu.com/security/notices/USN-7458-1
- https://ubuntu.com/security/notices/USN-7523-1
- https://ubuntu.com/security/notices/USN-7524-1
- https://www.cve.org/CVERecord?id=CVE-2024-50249