CVE-2023-52743
published 2024-05-21CVE-2023-52743: In the Linux kernel, the following vulnerability has been resolved: ice: Do not use WQ_MEM_RECLAIM flag for workqueue When both ice and the irdma driver are…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.24%
15.0th percentile
In the Linux kernel, the following vulnerability has been resolved:
ice: Do not use WQ_MEM_RECLAIM flag for workqueue
When both ice and the irdma driver are loaded, a warning in
check_flush_dependency is being triggered. This is due to ice driver
workqueue being allocated with the WQ_MEM_RECLAIM flag and the irdma one
is not.
According to kernel documentation, this flag should be set if the
workqueue will be involved in the kernel's memory reclamation flow.
Since it is not, there is no need for the ice driver's WQ to have this
flag set so remove it.
Example trace:
[ +0.000004] workqueue: WQ_MEM_RECLAIM ice:ice_service_task [ice] is flushing !WQ_MEM_RECLAIM infiniband:0x0
[ +0.000139] WARNING: CPU: 0 PID: 728 at kernel/workqueue.c:2632 check_flush_dependency+0x178/0x1a0
[ +0.000011] Modules linked in: bonding tls xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 nft_compat nft_cha
in_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc rfkill vfat fat intel_rapl_msr intel
_rapl_common isst_if_common skx_edac nfit libnvdimm x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct1
0dif_pclmul crc32_pclmul ghash_clmulni_intel rapl intel_cstate rpcrdma sunrpc rdma_ucm ib_srpt ib_isert iscsi_target_mod target_
core_mod ib_iser libiscsi scsi_transport_iscsi rdma_cm ib_cm iw_cm iTCO_wdt iTCO_vendor_support ipmi_ssif irdma mei_me ib_uverbs
ib_core intel_uncore joydev pcspkr i2c_i801 acpi_ipmi mei lpc_ich i2c_smbus intel_pch_thermal ioatdma ipmi_si acpi_power_meter
acpi_pad xfs libcrc32c sd_mod t10_pi crc64_rocksoft crc64 sg ahci ixgbe libahci ice i40e igb crc32c_intel mdio i2c_algo_bit liba
ta dca wmi dm_mirror dm_region_hash dm_log dm_mod ipmi_devintf ipmi_msghandler fuse
[ +0.000161] [last unloaded: bonding]
[ +0.000006] CPU: 0 PID: 728 Comm: kworker/0:2 Tainted: G S 6.2.0-rc2_next-queue-13jan-00458-gc20aabd57164 #1
[ +0.000006] Hardware name: Intel Corporation S2600WFT/S2600WFT, BIOS SE5C620.86B.0
Affected
16 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.12-1 (bookworm) | linux 6.1.12-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 940b61af02f497fcd911b9e2d75c6b8cf76b92fd < 87a5e3fc8416106e290c448fc8a6dd50ab24c634 | 87a5e3fc8416106e290c448fc8a6dd50ab24c634 |
| linux | linux | >= 940b61af02f497fcd911b9e2d75c6b8cf76b92fd < 1ad4112c9fcf0bc08222b2b1614fba52ffd12255 | 1ad4112c9fcf0bc08222b2b1614fba52ffd12255 |
| linux | linux | >= 940b61af02f497fcd911b9e2d75c6b8cf76b92fd < ca834a017851c50464c25a85f3cb2daefff7bede | ca834a017851c50464c25a85f3cb2daefff7bede |
| linux | linux | >= 940b61af02f497fcd911b9e2d75c6b8cf76b92fd < df59e05401450973c8c7e96fd74b49e24442dc1f | df59e05401450973c8c7e96fd74b49e24442dc1f |
| linux | linux | >= 940b61af02f497fcd911b9e2d75c6b8cf76b92fd < 4d159f7884f78b1aacb99b4fc37d1e3cb1194e39 | 4d159f7884f78b1aacb99b4fc37d1e3cb1194e39 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.178-1 | 5.10.178-1 |
| linux | linux_kernel | >= 0 < 6.1.12-1 | 6.1.12-1 |
| linux | linux_kernel | >= 0 < 6.1.12-1 | 6.1.12-1 |
| linux | linux_kernel | >= 0 < 6.1.12-1 | 6.1.12-1 |
| linux | linux_kernel | >= 4.17 < 5.4.232 | 5.4.232 |
| linux | linux_kernel | >= 5.11 < 5.15.94 | 5.15.94 |
| linux | linux_kernel | >= 5.16 < 6.1.12 | 6.1.12 |
| linux | linux_kernel | >= 5.5 < 5.10.168 | 5.10.168 |
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-9vvj-gw7c-qgmh: In the Linux kernel, the following vulnerability has been resolved:
ice: Do not use WQ_MEM_RECLAIM flag for workqueue
When both ice and the irdma dr
ghsa_unreviewed·2024-05-21
CVE-2023-52743 [MEDIUM] GHSA-9vvj-gw7c-qgmh: In the Linux kernel, the following vulnerability has been resolved:
ice: Do not use WQ_MEM_RECLAIM flag for workqueue
When both ice and the irdma dr
In the Linux kernel, the following vulnerability has been resolved:
ice: Do not use WQ_MEM_RECLAIM flag for workqueue
When both ice and the irdma driver are loaded, a warning in
check_flush_dependency is being triggered. This is due to ice driver
workqueue being allocated with the WQ_MEM_RECLAIM flag and the irdma one
is not.
According to kernel documentation, this flag should be set if the
workqueue will be involved in the kernel's memory reclamation flow.
Since it is not, there is no need for the ice driver's WQ to have this
flag set so remove it.
Example trace:
[ +0.000004] workqueue: WQ_MEM_RECLAIM ice:ice_service_task [ice] is flushing !WQ_MEM_RECLAIM infiniband:0x0
[ +0.000139] WARNING: CPU: 0 PID: 728 at kernel/workqueue.c:2632 check_flush_dependency+0x178/0x1a0
[ +0.000011] Mo
OSV
CVE-2023-52743: In the Linux kernel, the following vulnerability has been resolved: ice: Do not use WQ_MEM_RECLAIM flag for workqueue When both ice and the irdma driv
osv·2024-05-21·CVSS 5.5
CVE-2023-52743 [MEDIUM] CVE-2023-52743: In the Linux kernel, the following vulnerability has been resolved: ice: Do not use WQ_MEM_RECLAIM flag for workqueue When both ice and the irdma driv
In the Linux kernel, the following vulnerability has been resolved: ice: Do not use WQ_MEM_RECLAIM flag for workqueue When both ice and the irdma driver are loaded, a warning in check_flush_dependency is being triggered. This is due to ice driver workqueue being allocated with the WQ_MEM_RECLAIM flag and the irdma one is not. According to kernel documentation, this flag should be set if the workqueue will be involved in the kernel's memory reclamation flow. Since it is not, there is no need for the ice driver's WQ to have this flag set so remove it. Example trace: [ +0.000004] workqueue: WQ_MEM_RECLAIM ice:ice_service_task [ice] is flushing !WQ_MEM_RECLAIM infiniband:0x0 [ +0.000139] WARNING: CPU: 0 PID: 728 at kernel/workqueue.c:2632 check_flush_dependency+0x178/0x1a0 [ +0.000011] Modules
Red Hat
kernel: ice: Do not use WQ_MEM_RECLAIM flag for workqueue
vendor_redhat·2024-05-21·CVSS 5.5
CVE-2023-52743 [MEDIUM] CWE-99 kernel: ice: Do not use WQ_MEM_RECLAIM flag for workqueue
kernel: ice: Do not use WQ_MEM_RECLAIM flag for workqueue
In the Linux kernel, the following vulnerability has been resolved:
ice: Do not use WQ_MEM_RECLAIM flag for workqueue
When both ice and the irdma driver are loaded, a warning in
check_flush_dependency is being triggered. This is due to ice driver
workqueue being allocated with the WQ_MEM_RECLAIM flag and the irdma one
is not.
According to kernel documentation, this flag should be set if the
workqueue will be involved in the kernel's memory reclamation flow.
Since it is not, there is no need for the ice driver's WQ to have this
flag set so remove it.
Example trace:
[ +0.000004] workqueue: WQ_MEM_RECLAIM ice:ice_service_task [ice] is flushing !WQ_MEM_RECLAIM infiniband:0x0
[ +0.000139] WARNING: CPU: 0 PID: 728 at kernel/workqueue.c:2
Debian
CVE-2023-52743: linux - In the Linux kernel, the following vulnerability has been resolved: ice: Do not...
vendor_debian·2023·CVSS 5.5
CVE-2023-52743 [MEDIUM] CVE-2023-52743: linux - In the Linux kernel, the following vulnerability has been resolved: ice: Do not...
In the Linux kernel, the following vulnerability has been resolved: ice: Do not use WQ_MEM_RECLAIM flag for workqueue When both ice and the irdma driver are loaded, a warning in check_flush_dependency is being triggered. This is due to ice driver workqueue being allocated with the WQ_MEM_RECLAIM flag and the irdma one is not. According to kernel documentation, this flag should be set if the workqueue will be involved in the kernel's memory reclamation flow. Since it is not, there is no need for the ice driver's WQ to have this flag set so remove it. Example trace: [ +0.000004] workqueue: WQ_MEM_RECLAIM ice:ice_service_task [ice] is flushing !WQ_MEM_RECLAIM infiniband:0x0 [ +0.000139] WARNING: CPU: 0 PID: 728 at kernel/workqueue.c:2632 check_flush_dependency+0x178/0x1a0 [ +0.000011] Modules
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/1ad4112c9fcf0bc08222b2b1614fba52ffd12255https://git.kernel.org/stable/c/4d159f7884f78b1aacb99b4fc37d1e3cb1194e39https://git.kernel.org/stable/c/87a5e3fc8416106e290c448fc8a6dd50ab24c634https://git.kernel.org/stable/c/ca834a017851c50464c25a85f3cb2daefff7bedehttps://git.kernel.org/stable/c/df59e05401450973c8c7e96fd74b49e24442dc1fhttps://git.kernel.org/stable/c/1ad4112c9fcf0bc08222b2b1614fba52ffd12255https://git.kernel.org/stable/c/4d159f7884f78b1aacb99b4fc37d1e3cb1194e39https://git.kernel.org/stable/c/87a5e3fc8416106e290c448fc8a6dd50ab24c634https://git.kernel.org/stable/c/ca834a017851c50464c25a85f3cb2daefff7bedehttps://git.kernel.org/stable/c/df59e05401450973c8c7e96fd74b49e24442dc1f
2024-05-21
Published