CVE-2021-47056
published 2024-02-29CVE-2021-47056: In the Linux kernel, the following vulnerability has been resolved: crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init ADF_STATUS_PF_RUNNING…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.23%
13.4th percentile
In the Linux kernel, the following vulnerability has been resolved:
crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init
ADF_STATUS_PF_RUNNING is (only) used and checked by adf_vf2pf_shutdown()
before calling adf_iov_putmsg()->mutex_lock(vf2pf_lock), however the
vf2pf_lock is initialized in adf_dev_init(), which can fail and when it
fail, the vf2pf_lock is either not initialized or destroyed, a subsequent
use of vf2pf_lock will cause issue.
To fix this issue, only set this flag if adf_dev_init() returns 0.
[ 7.178404] BUG: KASAN: user-memory-access in __mutex_lock.isra.0+0x1ac/0x7c0
[ 7.180345] Call Trace:
[ 7.182576] mutex_lock+0xc9/0xd0
[ 7.183257] adf_iov_putmsg+0x118/0x1a0 [intel_qat]
[ 7.183541] adf_vf2pf_shutdown+0x4d/0x7b [intel_qat]
[ 7.183834] adf_dev_shutdown+0x172/0x2b0 [intel_qat]
[ 7.184127] adf_probe+0x5e9/0x600 [qat_dh895xccvf]
Affected
21 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.10.38-1 (bookworm) | linux 5.10.38-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 25c6ffb249f612c56a48ce48a3887adf57b8f4bd < f4c4e07140687f42bfa40e091bb4a55d7960ce4d | f4c4e07140687f42bfa40e091bb4a55d7960ce4d |
| linux | linux | >= 25c6ffb249f612c56a48ce48a3887adf57b8f4bd < 446045cf682af12d9294765f6c46084b374b5654 | 446045cf682af12d9294765f6c46084b374b5654 |
| linux | linux | >= 25c6ffb249f612c56a48ce48a3887adf57b8f4bd < 09d16cee6285d37cc76311c29add6d97a7e4acda | 09d16cee6285d37cc76311c29add6d97a7e4acda |
| linux | linux | >= 25c6ffb249f612c56a48ce48a3887adf57b8f4bd < 05ec8192ee4bfdf2a8894a68350dac9f1a155fa6 | 05ec8192ee4bfdf2a8894a68350dac9f1a155fa6 |
| linux | linux | >= 25c6ffb249f612c56a48ce48a3887adf57b8f4bd < 1f50392650ae794a1aea41c213c6a3e1c824413c | 1f50392650ae794a1aea41c213c6a3e1c824413c |
| linux | linux | >= 25c6ffb249f612c56a48ce48a3887adf57b8f4bd < 20fd40fc6f2c2b41dc6f637f88d494b14e9c21f1 | 20fd40fc6f2c2b41dc6f637f88d494b14e9c21f1 |
| linux | linux | >= 25c6ffb249f612c56a48ce48a3887adf57b8f4bd < 1ea500ce6f7c9106e4a561d28e69215f3d451818 | 1ea500ce6f7c9106e4a561d28e69215f3d451818 |
| linux | linux | >= 25c6ffb249f612c56a48ce48a3887adf57b8f4bd < 8609f5cfdc872fc3a462efa6a3eca5cb1e2f6446 | 8609f5cfdc872fc3a462efa6a3eca5cb1e2f6446 |
| linux | linux_kernel | >= 0 < 5.10.38-1 | 5.10.38-1 |
| linux | linux_kernel | >= 0 < 5.10.38-1 | 5.10.38-1 |
| linux | linux_kernel | >= 0 < 5.10.38-1 | 5.10.38-1 |
| linux | linux_kernel | >= 0 < 5.10.38-1 | 5.10.38-1 |
| linux | linux_kernel | >= 4.10 < 4.14.233 | 4.14.233 |
| linux | linux_kernel | >= 4.15 < 4.19.191 | 4.19.191 |
| linux | linux_kernel | >= 4.20 < 5.4.119 | 5.4.119 |
| linux | linux_kernel | >= 4.7 < 4.9.269 | 4.9.269 |
| linux | linux_kernel | >= 5.11 < 5.11.21 | 5.11.21 |
| linux | linux_kernel | >= 5.12 < 5.12.4 | 5.12.4 |
| linux | linux_kernel | >= 5.5 < 5.10.37 | 5.10.37 |
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.
Red Hat
kernel: crypto: denial-of-service in ADF_STATUS_PF_RUNNING should be set after adf_dev_init
vendor_redhat·2024-02-29·CVSS 5.5
CVE-2021-47056 [MEDIUM] CWE-413 kernel: crypto: denial-of-service in ADF_STATUS_PF_RUNNING should be set after adf_dev_init
kernel: crypto: denial-of-service in ADF_STATUS_PF_RUNNING should be set after adf_dev_init
In the Linux kernel, the following vulnerability has been resolved:
crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init
ADF_STATUS_PF_RUNNING is (only) used and checked by adf_vf2pf_shutdown()
before calling adf_iov_putmsg()->mutex_lock(vf2pf_lock), however the
vf2pf_lock is initialized in adf_dev_init(), which can fail and when it
fail, the vf2pf_lock is either not initialized or destroyed, a subsequent
use of vf2pf_lock will cause issue.
To fix this issue, only set this flag if adf_dev_init() returns 0.
[ 7.178404] BUG: KASAN: user-memory-access in __mutex_lock.isra.0+0x1ac/0x7c0
[ 7.180345] Call Trace:
[ 7.182576] mutex_lock+0xc9/0xd0
[ 7.183257] adf_iov_putmsg+0x118/0x1a0 [inte
Debian
CVE-2021-47056: linux - In the Linux kernel, the following vulnerability has been resolved: crypto: qat...
vendor_debian·2021·CVSS 5.5
CVE-2021-47056 [MEDIUM] CVE-2021-47056: linux - In the Linux kernel, the following vulnerability has been resolved: crypto: qat...
In the Linux kernel, the following vulnerability has been resolved: crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init ADF_STATUS_PF_RUNNING is (only) used and checked by adf_vf2pf_shutdown() before calling adf_iov_putmsg()->mutex_lock(vf2pf_lock), however the vf2pf_lock is initialized in adf_dev_init(), which can fail and when it fail, the vf2pf_lock is either not initialized or destroyed, a subsequent use of vf2pf_lock will cause issue. To fix this issue, only set this flag if adf_dev_init() returns 0. [ 7.178404] BUG: KASAN: user-memory-access in __mutex_lock.isra.0+0x1ac/0x7c0 [ 7.180345] Call Trace: [ 7.182576] mutex_lock+0xc9/0xd0 [ 7.183257] adf_iov_putmsg+0x118/0x1a0 [intel_qat] [ 7.183541] adf_vf2pf_shutdown+0x4d/0x7b [intel_qat] [ 7.183834] adf_dev_shutdown+0x17
GHSA
GHSA-5fwg-75w6-7gf9: In the Linux kernel, the following vulnerability has been resolved:
crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init
ADF_STATUS_
ghsa_unreviewed·2024-03-01
CVE-2021-47056 [MEDIUM] CWE-908 GHSA-5fwg-75w6-7gf9: In the Linux kernel, the following vulnerability has been resolved:
crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init
ADF_STATUS_
In the Linux kernel, the following vulnerability has been resolved:
crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init
ADF_STATUS_PF_RUNNING is (only) used and checked by adf_vf2pf_shutdown()
before calling adf_iov_putmsg()->mutex_lock(vf2pf_lock), however the
vf2pf_lock is initialized in adf_dev_init(), which can fail and when it
fail, the vf2pf_lock is either not initialized or destroyed, a subsequent
use of vf2pf_lock will cause issue.
To fix this issue, only set this flag if adf_dev_init() returns 0.
[ 7.178404] BUG: KASAN: user-memory-access in __mutex_lock.isra.0+0x1ac/0x7c0
[ 7.180345] Call Trace:
[ 7.182576] mutex_lock+0xc9/0xd0
[ 7.183257] adf_iov_putmsg+0x118/0x1a0 [intel_qat]
[ 7.183541] adf_vf2pf_shutdown+0x4d/0x7b [intel_qat]
[ 7.183834] adf_dev_shutdown+0
OSV
CVE-2021-47056: In the Linux kernel, the following vulnerability has been resolved: crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init ADF_STATUS_PF
osv·2024-02-29·CVSS 5.5
CVE-2021-47056 [MEDIUM] CVE-2021-47056: In the Linux kernel, the following vulnerability has been resolved: crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init ADF_STATUS_PF
In the Linux kernel, the following vulnerability has been resolved: crypto: qat - ADF_STATUS_PF_RUNNING should be set after adf_dev_init ADF_STATUS_PF_RUNNING is (only) used and checked by adf_vf2pf_shutdown() before calling adf_iov_putmsg()->mutex_lock(vf2pf_lock), however the vf2pf_lock is initialized in adf_dev_init(), which can fail and when it fail, the vf2pf_lock is either not initialized or destroyed, a subsequent use of vf2pf_lock will cause issue. To fix this issue, only set this flag if adf_dev_init() returns 0. [ 7.178404] BUG: KASAN: user-memory-access in __mutex_lock.isra.0+0x1ac/0x7c0 [ 7.180345] Call Trace: [ 7.182576] mutex_lock+0xc9/0xd0 [ 7.183257] adf_iov_putmsg+0x118/0x1a0 [intel_qat] [ 7.183541] adf_vf2pf_shutdown+0x4d/0x7b [intel_qat] [ 7.183834] adf_dev_shutdown+0x17
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/05ec8192ee4bfdf2a8894a68350dac9f1a155fa6https://git.kernel.org/stable/c/09d16cee6285d37cc76311c29add6d97a7e4acdahttps://git.kernel.org/stable/c/1ea500ce6f7c9106e4a561d28e69215f3d451818https://git.kernel.org/stable/c/1f50392650ae794a1aea41c213c6a3e1c824413chttps://git.kernel.org/stable/c/20fd40fc6f2c2b41dc6f637f88d494b14e9c21f1https://git.kernel.org/stable/c/446045cf682af12d9294765f6c46084b374b5654https://git.kernel.org/stable/c/8609f5cfdc872fc3a462efa6a3eca5cb1e2f6446https://git.kernel.org/stable/c/f4c4e07140687f42bfa40e091bb4a55d7960ce4dhttps://git.kernel.org/stable/c/05ec8192ee4bfdf2a8894a68350dac9f1a155fa6https://git.kernel.org/stable/c/09d16cee6285d37cc76311c29add6d97a7e4acdahttps://git.kernel.org/stable/c/1ea500ce6f7c9106e4a561d28e69215f3d451818https://git.kernel.org/stable/c/1f50392650ae794a1aea41c213c6a3e1c824413chttps://git.kernel.org/stable/c/20fd40fc6f2c2b41dc6f637f88d494b14e9c21f1https://git.kernel.org/stable/c/446045cf682af12d9294765f6c46084b374b5654https://git.kernel.org/stable/c/8609f5cfdc872fc3a462efa6a3eca5cb1e2f6446https://git.kernel.org/stable/c/f4c4e07140687f42bfa40e091bb4a55d7960ce4d
2024-02-29
Published