Show filters
6 Total Results
Displaying 1-6 of 6
Sort by:
Attacker Value
Unknown

CVE-2019-16233

Disclosure Date: September 11, 2019 (last updated November 27, 2024)
drivers/scsi/qla2xxx/qla_os.c in the Linux kernel 5.2.14 does not check the alloc_workqueue return value, leading to a NULL pointer dereference.
Attacker Value
Unknown

CVE-2019-16230

Disclosure Date: September 11, 2019 (last updated November 08, 2023)
drivers/gpu/drm/radeon/radeon_display.c in the Linux kernel 5.2.14 does not check the alloc_workqueue return value, leading to a NULL pointer dereference. NOTE: A third-party software maintainer states that the work queue allocation is happening during device initialization, which for a graphics card occurs during boot. It is not attacker controllable and OOM at that time is highly unlikely
Attacker Value
Unknown

CVE-2019-16232

Disclosure Date: September 11, 2019 (last updated November 08, 2023)
drivers/net/wireless/marvell/libertas/if_sdio.c in the Linux kernel 5.2.14 does not check the alloc_workqueue return value, leading to a NULL pointer dereference.
Attacker Value
Unknown

CVE-2019-16234

Disclosure Date: September 11, 2019 (last updated November 27, 2024)
drivers/net/wireless/intel/iwlwifi/pcie/trans.c in the Linux kernel 5.2.14 does not check the alloc_workqueue return value, leading to a NULL pointer dereference.
Attacker Value
Unknown

CVE-2019-16231

Disclosure Date: September 11, 2019 (last updated November 27, 2024)
drivers/net/fjes/fjes_main.c in the Linux kernel 5.2.14 does not check the alloc_workqueue return value, leading to a NULL pointer dereference.
Attacker Value
Unknown

CVE-2019-16229

Disclosure Date: September 11, 2019 (last updated November 08, 2023)
drivers/gpu/drm/amd/amdkfd/kfd_interrupt.c in the Linux kernel 5.2.14 does not check the alloc_workqueue return value, leading to a NULL pointer dereference. NOTE: The security community disputes this issues as not being serious enough to be deserving a CVE id