CVE-2021-47583
published 2024-06-19CVE-2021-47583: In the Linux kernel, the following vulnerability has been resolved: media: mxl111sf: change mutex_init() location Syzbot reported, that mxl111sf_ctrl_msg()…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.24%
15.0th percentile
In the Linux kernel, the following vulnerability has been resolved:
media: mxl111sf: change mutex_init() location
Syzbot reported, that mxl111sf_ctrl_msg() uses uninitialized
mutex. The problem was in wrong mutex_init() location.
Previous mutex_init(&state->msg_lock) call was in ->init() function, but
dvb_usbv2_init() has this order of calls:
dvb_usbv2_init()
dvb_usbv2_adapter_init()
dvb_usbv2_adapter_frontend_init()
props->frontend_attach()
props->init()
Since mxl111sf_* devices call mxl111sf_ctrl_msg() in ->frontend_attach()
internally we need to initialize state->msg_lock before
frontend_attach(). To achieve it, ->probe() call added to all mxl111sf_*
devices, which will simply initiaize mutex.
Affected
15 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.15.15-1 (bookworm) | linux 5.15.15-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 8572211842afc53c8450fb470f2b8d02ba7592e0 < 4b2d9600b31f9ba7adbc9f3c54a068615d27b390 | 4b2d9600b31f9ba7adbc9f3c54a068615d27b390 |
| linux | linux | >= 8572211842afc53c8450fb470f2b8d02ba7592e0 < 96f182c9f48b984447741f054ec301fdc8517035 | 96f182c9f48b984447741f054ec301fdc8517035 |
| linux | linux | >= 8572211842afc53c8450fb470f2b8d02ba7592e0 < b99bdf127af91d53919e96292c05f737c45ea59a | b99bdf127af91d53919e96292c05f737c45ea59a |
| linux | linux | >= 8572211842afc53c8450fb470f2b8d02ba7592e0 < 8c6fdf62bfe1bc72bfceeaf832ef7499c7ed09ba | 8c6fdf62bfe1bc72bfceeaf832ef7499c7ed09ba |
| linux | linux | >= 8572211842afc53c8450fb470f2b8d02ba7592e0 < 44870a9e7a3c24acbb3f888b2a7cc22c9bdf7e7f | 44870a9e7a3c24acbb3f888b2a7cc22c9bdf7e7f |
| linux | linux_kernel | >= 0 < 5.10.92-1 | 5.10.92-1 |
| linux | linux_kernel | >= 0 < 5.15.15-1 | 5.15.15-1 |
| linux | linux_kernel | >= 0 < 5.15.15-1 | 5.15.15-1 |
| linux | linux_kernel | >= 0 < 5.15.15-1 | 5.15.15-1 |
| linux | linux_kernel | >= 3.7 < 4.19.222 | 4.19.222 |
| linux | linux_kernel | >= 4.20 < 5.4.168 | 5.4.168 |
| linux | linux_kernel | >= 5.11 < 5.15.11 | 5.15.11 |
| linux | linux_kernel | >= 5.5 < 5.10.88 | 5.10.88 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2021-47583: In the Linux kernel, the following vulnerability has been resolved: media: mxl111sf: change mutex_init() location Syzbot reported, that mxl111sf_ctrl_
osv·2024-06-19·CVSS 5.5
CVE-2021-47583 [MEDIUM] CVE-2021-47583: In the Linux kernel, the following vulnerability has been resolved: media: mxl111sf: change mutex_init() location Syzbot reported, that mxl111sf_ctrl_
In the Linux kernel, the following vulnerability has been resolved: media: mxl111sf: change mutex_init() location Syzbot reported, that mxl111sf_ctrl_msg() uses uninitialized mutex. The problem was in wrong mutex_init() location. Previous mutex_init(&state->msg_lock) call was in ->init() function, but dvb_usbv2_init() has this order of calls: dvb_usbv2_init() dvb_usbv2_adapter_init() dvb_usbv2_adapter_frontend_init() props->frontend_attach() props->init() Since mxl111sf_* devices call mxl111sf_ctrl_msg() in ->frontend_attach() internally we need to initialize state->msg_lock before frontend_attach(). To achieve it, ->probe() call added to all mxl111sf_* devices, which will simply initiaize mutex.
GHSA
GHSA-hfwg-2mm4-h8c4: In the Linux kernel, the following vulnerability has been resolved:
media: mxl111sf: change mutex_init() location
Syzbot reported, that mxl111sf_ctr
ghsa_unreviewed·2024-06-19
CVE-2021-47583 [MEDIUM] CWE-908 GHSA-hfwg-2mm4-h8c4: In the Linux kernel, the following vulnerability has been resolved:
media: mxl111sf: change mutex_init() location
Syzbot reported, that mxl111sf_ctr
In the Linux kernel, the following vulnerability has been resolved:
media: mxl111sf: change mutex_init() location
Syzbot reported, that mxl111sf_ctrl_msg() uses uninitialized
mutex. The problem was in wrong mutex_init() location.
Previous mutex_init(&state->msg_lock) call was in ->init() function, but
dvb_usbv2_init() has this order of calls:
dvb_usbv2_init()
dvb_usbv2_adapter_init()
dvb_usbv2_adapter_frontend_init()
props->frontend_attach()
props->init()
Since mxl111sf_* devices call mxl111sf_ctrl_msg() in ->frontend_attach()
internally we need to initialize state->msg_lock before
frontend_attach(). To achieve it, ->probe() call added to all mxl111sf_*
devices, which will simply initiaize mutex.
Red Hat
kernel: media: mxl111sf: change mutex_init() location
vendor_redhat·2024-06-19·CVSS 5.5
CVE-2021-47583 [MEDIUM] CWE-908 kernel: media: mxl111sf: change mutex_init() location
kernel: media: mxl111sf: change mutex_init() location
In the Linux kernel, the following vulnerability has been resolved:
media: mxl111sf: change mutex_init() location
Syzbot reported, that mxl111sf_ctrl_msg() uses uninitialized
mutex. The problem was in wrong mutex_init() location.
Previous mutex_init(&state->msg_lock) call was in ->init() function, but
dvb_usbv2_init() has this order of calls:
dvb_usbv2_init()
dvb_usbv2_adapter_init()
dvb_usbv2_adapter_frontend_init()
props->frontend_attach()
props->init()
Since mxl111sf_* devices call mxl111sf_ctrl_msg() in ->frontend_attach()
internally we need to initialize state->msg_lock before
frontend_attach(). To achieve it, ->probe() call added to all mxl111sf_*
devices, which will simply initiaize mutex.
Package: kernel (Red Hat Enterprise Li
Debian
CVE-2021-47583: linux - In the Linux kernel, the following vulnerability has been resolved: media: mxl1...
vendor_debian·2021·CVSS 5.5
CVE-2021-47583 [MEDIUM] CVE-2021-47583: linux - In the Linux kernel, the following vulnerability has been resolved: media: mxl1...
In the Linux kernel, the following vulnerability has been resolved: media: mxl111sf: change mutex_init() location Syzbot reported, that mxl111sf_ctrl_msg() uses uninitialized mutex. The problem was in wrong mutex_init() location. Previous mutex_init(&state->msg_lock) call was in ->init() function, but dvb_usbv2_init() has this order of calls: dvb_usbv2_init() dvb_usbv2_adapter_init() dvb_usbv2_adapter_frontend_init() props->frontend_attach() props->init() Since mxl111sf_* devices call mxl111sf_ctrl_msg() in ->frontend_attach() internally we need to initialize state->msg_lock before frontend_attach(). To achieve it, ->probe() call added to all mxl111sf_* devices, which will simply initiaize mutex.
Scope: local
bookworm: resolved (fixed in 5.15.15-1)
bullseye: resolved (fixed in 5.10.92-1)
f
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://git.kernel.org/stable/c/44870a9e7a3c24acbb3f888b2a7cc22c9bdf7e7fhttps://git.kernel.org/stable/c/4b2d9600b31f9ba7adbc9f3c54a068615d27b390https://git.kernel.org/stable/c/8c6fdf62bfe1bc72bfceeaf832ef7499c7ed09bahttps://git.kernel.org/stable/c/96f182c9f48b984447741f054ec301fdc8517035https://git.kernel.org/stable/c/b99bdf127af91d53919e96292c05f737c45ea59ahttps://git.kernel.org/stable/c/44870a9e7a3c24acbb3f888b2a7cc22c9bdf7e7fhttps://git.kernel.org/stable/c/4b2d9600b31f9ba7adbc9f3c54a068615d27b390https://git.kernel.org/stable/c/8c6fdf62bfe1bc72bfceeaf832ef7499c7ed09bahttps://git.kernel.org/stable/c/96f182c9f48b984447741f054ec301fdc8517035https://git.kernel.org/stable/c/b99bdf127af91d53919e96292c05f737c45ea59a
2024-06-19
Published