6 matches found
CVE-2023-52743 ice: Do not use WQ_MEM_RECLAIM flag for workqueue
In the Linux kernel, the following vulnerability has been resolved: ice: Do not use WQMEMRECLAIM flag for workqueue When both ice and the irdma driver are loaded, a warning in checkflushdependency is being triggered. This is due to ice driver workqueue being allocated with the WQMEMRECLAIM flag a...
CVE-2023-52743 ice: Do not use WQ_MEM_RECLAIM flag for workqueue
In the Linux kernel, the following vulnerability has been resolved: ice: Do not use WQMEMRECLAIM flag for workqueue When both ice and the irdma driver are loaded, a warning in checkflushdependency is being triggered. This is due to ice driver workqueue being allocated with the WQMEMRECLAIM flag a...
CVE-2023-52743: Undefined Security Weakness
In the Linux kernel, the following vulnerability has been resolved: ice: Do not use WQMEMRECLAIM flag for workqueue When both ice and the irdma driver are loaded, a warning in checkflushdependency is being triggered. This is due to ice driver workqueue being allocated with the WQMEMRECLAIM flag a...
CVE-2024-36004 i40e: Do not use WQ_MEM_RECLAIM flag for workqueue
In the Linux kernel, the following vulnerability has been resolved: i40e: Do not use WQMEMRECLAIM flag for workqueue Issue reported by customer during SRIOV testing, call trace: When both i40e and the i40iw driver are loaded, a warning in checkflushdependency is being triggered. This seems to be...
Design/Logic Flaw
In the Linux kernel, the following vulnerability has been resolved: bus: mhi: pcigeneric: Remove WQMEMRECLAIM flag from state workqueue A recent change created a dedicated workqueue for the state-change work with WQHIGHPRI no strong reason for that and WQMEMRECLAIM flags, but the state-change wor...
UVI-2021-1000087 bus: mhi: pci_generic: Remove WQ_MEM_RECLAIM flag from state workqueue
bus: mhi: pcigeneric: Remove WQMEMRECLAIM flag from state workqueue This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven. This ID is fixed in Linux Kernel version v5.12.3 by commit...