slimbus: qcom-ngd-ctrl: Register callbacks after creating the ngd
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 08564e15c47a5fb0af6643a43ee15521d49bcdea, Kernel 2047eeb38db878a31f58db19d98f8aedf284342e, Kernel 24ec89123fc9d0d24ce719dcf7fd6c57e5b0d753 and 5 more.
In the Linux kernel, the following vulnerability has been resolved: slimbus: qcom-ngd-ctrl: Register callbacks after creating the ngd When the remoteproc starts in parallel with the NGD driver being probed, or the remoteproc is already up when the PDR lookup is being registered, or in the theoretical event that we get an interrupt from the hardware, these callbacks will operate on uninitialized data. This result in issues to boot the affected boards. One such example can be seen in the following fault, where qcom_slim_ngd_ssr_pdr_notify() schedules work on the NULL ngd_up_work. [ 21.858578] ------------[ cut here ]------------ [ 21.858745] WARNING: kernel/workqueue.c:2338 at __queue_work+0x5e0/0x790, CPU#2: kworker/2:2/116 ... [ 21.859251] Call trace: [ 21.859255] __queue_work+0x5e0/0x790 (P) [ 21.859265] queue_work_on+0x6c/0xf0 [ 21.859273] qcom_slim_ngd_ssr_pdr_notify+0x110/0x150 [slim_qcom_ngd_ctrl] [ 21.859304] qcom_slim_ngd_ssr_notify+0x24/0x40 [slim_qcom_ngd_ctrl] [ 21.859318] notifier_call_chain+0xa4/0x230 [ 21.859329] srcu_notifier_call_chain+0x64/0xb8 [ 21.859338] ssr_notify_start+0x40/0x78 [qcom_common] [ 21.859355] rproc_start+0x130/0x230 [ 21.859367] rproc_boot+0x3d4/0x518 ... Move the enablement of interrupts, and the registration of SSR and PDR until after the NGD device has been registered. This could be further refined by moving initialization to the control driver probe and by removing the platform driver model from the picture.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =4.19, >=917809e2280bb83994be8b642373fd941d40c407 <08564e15c47a5fb0af6643a43ee15521d49bcdea, >=917809e2280bb83994be8b642373fd941d40c407 <2047eeb38db878a31f58db19d98f8aedf284342e, >=917809e2280bb83994be8b642373fd941d40c407 <24ec89123fc9d0d24ce719dcf7fd6c57e5b0d753, >=917809e2280bb83994be8b642373fd941d40c407 <290014c7987636e6105bba89fa04cb4d59f775c1, >=917809e2280bb83994be8b642373fd941d40c407 <2a9d50e9ea406e0c8735938484adc20515ef1b47, >=917809e2280bb83994be8b642373fd941d40c407 <946b97d632f0f58a705dafac644c1e9346e01f35, >=917809e2280bb83994be8b642373fd941d40c407 <afc631e246936a40558f494112a4188401382671, >=917809e2280bb83994be8b642373fd941d40c407 <fa3790c7ea98328ddc3f7d8bf40247556245a6fc | 08564e15c47a5fb0af6643a43ee15521d49bcdea, 2047eeb38db878a31f58db19d98f8aedf284342e, 24ec89123fc9d0d24ce719dcf7fd6c57e5b0d753, 290014c7987636e6105bba89fa04cb4d59f775c1, 2a9d50e9ea406e0c8735938484adc20515ef1b47, 946b97d632f0f58a705dafac644c1e9346e01f35, afc631e246936a40558f494112a4188401382671, fa3790c7ea98328ddc3f7d8bf40247556245a6fc |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket