CVE-2021-47037
published 2024-02-28CVE-2021-47037: In the Linux kernel, the following vulnerability has been resolved: ASoC: q6afe-clocks: fix reprobing of the driver Q6afe-clocks driver can get reprobed. For…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.24%
15.0th percentile
In the Linux kernel, the following vulnerability has been resolved:
ASoC: q6afe-clocks: fix reprobing of the driver
Q6afe-clocks driver can get reprobed. For example if the APR services
are restarted after the firmware crash. However currently Q6afe-clocks
driver will oops because hw.init will get cleared during first _probe
call. Rewrite the driver to fill the clock data at runtime rather than
using big static array of clocks.
Affected
12 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.14.6-1 (bookworm) | linux 5.14.6-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 520a1c396d1966b64884d8e0176a580150d5a09e < 2202e87fc19440cecfd4f7b4f60a7d48bc2e236c | 2202e87fc19440cecfd4f7b4f60a7d48bc2e236c |
| linux | linux | >= 520a1c396d1966b64884d8e0176a580150d5a09e < 6893df3753beafa5f7351228a9dd8157a57d7492 | 6893df3753beafa5f7351228a9dd8157a57d7492 |
| linux | linux | >= 520a1c396d1966b64884d8e0176a580150d5a09e < 62413972f5266568848a36fd15160397b211fa74 | 62413972f5266568848a36fd15160397b211fa74 |
| linux | linux | >= 520a1c396d1966b64884d8e0176a580150d5a09e < 96fadf7e8ff49fdb74754801228942b67c3eeebd | 96fadf7e8ff49fdb74754801228942b67c3eeebd |
| linux | linux_kernel | >= 0 < 5.10.244-1 | 5.10.244-1 |
| linux | linux_kernel | >= 0 < 5.14.6-1 | 5.14.6-1 |
| linux | linux_kernel | >= 0 < 5.14.6-1 | 5.14.6-1 |
| linux | linux_kernel | >= 0 < 5.14.6-1 | 5.14.6-1 |
| linux | linux_kernel | >= 5.10 < 5.11.21 | 5.11.21 |
| linux | linux_kernel | >= 5.12 < 5.12.4 | 5.12.4 |
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.
GHSA
GHSA-8xhh-j9m8-989c: In the Linux kernel, the following vulnerability has been resolved:
ASoC: q6afe-clocks: fix reprobing of the driver
Q6afe-clocks driver can get repr
ghsa_unreviewed·2024-02-28
CVE-2021-47037 [MEDIUM] GHSA-8xhh-j9m8-989c: In the Linux kernel, the following vulnerability has been resolved:
ASoC: q6afe-clocks: fix reprobing of the driver
Q6afe-clocks driver can get repr
In the Linux kernel, the following vulnerability has been resolved:
ASoC: q6afe-clocks: fix reprobing of the driver
Q6afe-clocks driver can get reprobed. For example if the APR services
are restarted after the firmware crash. However currently Q6afe-clocks
driver will oops because hw.init will get cleared during first _probe
call. Rewrite the driver to fill the clock data at runtime rather than
using big static array of clocks.
OSV
CVE-2021-47037: In the Linux kernel, the following vulnerability has been resolved: ASoC: q6afe-clocks: fix reprobing of the driver Q6afe-clocks driver can get reprob
osv·2024-02-28·CVSS 5.5
CVE-2021-47037 [MEDIUM] CVE-2021-47037: In the Linux kernel, the following vulnerability has been resolved: ASoC: q6afe-clocks: fix reprobing of the driver Q6afe-clocks driver can get reprob
In the Linux kernel, the following vulnerability has been resolved: ASoC: q6afe-clocks: fix reprobing of the driver Q6afe-clocks driver can get reprobed. For example if the APR services are restarted after the firmware crash. However currently Q6afe-clocks driver will oops because hw.init will get cleared during first _probe call. Rewrite the driver to fill the clock data at runtime rather than using big static array of clocks.
Red Hat
kernel: ASoC: q6afe-clocks: fix reprobing of the driver
vendor_redhat·2024-02-28·CVSS 5.5
CVE-2021-47037 [MEDIUM] CWE-400 kernel: ASoC: q6afe-clocks: fix reprobing of the driver
kernel: ASoC: q6afe-clocks: fix reprobing of the driver
In the Linux kernel, the following vulnerability has been resolved:
ASoC: q6afe-clocks: fix reprobing of the driver
Q6afe-clocks driver can get reprobed. For example if the APR services
are restarted after the firmware crash. However currently Q6afe-clocks
driver will oops because hw.init will get cleared during first _probe
call. Rewrite the driver to fill the clock data at runtime rather than
using big static array of clocks.
Package: kernel (Red Hat Enterprise Linux 6) - Out of support scope
Package: kernel (Red Hat Enterprise Linux 7) - Out of support scope
Package: kernel-rt (Red Hat Enterprise Linux 7) - Out of support scope
Package: kernel (Red Hat Enterprise Linux 8) - Not affected
Package: kernel-rt (Red Hat Enterprise
Debian
CVE-2021-47037: linux - In the Linux kernel, the following vulnerability has been resolved: ASoC: q6afe...
vendor_debian·2021·CVSS 5.5
CVE-2021-47037 [MEDIUM] CVE-2021-47037: linux - In the Linux kernel, the following vulnerability has been resolved: ASoC: q6afe...
In the Linux kernel, the following vulnerability has been resolved: ASoC: q6afe-clocks: fix reprobing of the driver Q6afe-clocks driver can get reprobed. For example if the APR services are restarted after the firmware crash. However currently Q6afe-clocks driver will oops because hw.init will get cleared during first _probe call. Rewrite the driver to fill the clock data at runtime rather than using big static array of clocks.
Scope: local
bookworm: resolved (fixed in 5.14.6-1)
bullseye: resolved (fixed in 5.10.244-1)
forky: resolved (fixed in 5.14.6-1)
sid: resolved (fixed in 5.14.6-1)
trixie: resolved (fixed in 5.14.6-1)
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/2202e87fc19440cecfd4f7b4f60a7d48bc2e236chttps://git.kernel.org/stable/c/62413972f5266568848a36fd15160397b211fa74https://git.kernel.org/stable/c/6893df3753beafa5f7351228a9dd8157a57d7492https://git.kernel.org/stable/c/96fadf7e8ff49fdb74754801228942b67c3eeebdhttps://git.kernel.org/stable/c/62413972f5266568848a36fd15160397b211fa74https://git.kernel.org/stable/c/6893df3753beafa5f7351228a9dd8157a57d7492https://git.kernel.org/stable/c/96fadf7e8ff49fdb74754801228942b67c3eeebdhttps://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
2024-02-28
Published