1538 matches found
DEBIAN-CVE-2023-53223
In the Linux kernel, the following vulnerability has been resolved: drm/msm/dsi: Add missing check for allocorderedworkqueue Add check for the return value of allocorderedworkqueue as it may return NULL pointer and cause NULL pointer dereference. Patchwork:...
UBUNTU-CVE-2023-53223
In the Linux kernel, the following vulnerability has been resolved: drm/msm/dsi: Add missing check for allocorderedworkqueue Add check for the return value of allocorderedworkqueue as it may return NULL pointer and cause NULL pointer dereference. Patchwork:...
CVE-2023-53233 net/smc: fix deadlock triggered by cancel_delayed_work_syn()
In the Linux kernel, the following vulnerability has been resolved: net/smc: fix deadlock triggered by canceldelayedworksyn The following LOCKDEP was detected: Workqueue: events smclgrfreework smc WARNING: possible circular locking dependency detected...
CVE-2023-53223 drm/msm/dsi: Add missing check for alloc_ordered_workqueue
In the Linux kernel, the following vulnerability has been resolved: drm/msm/dsi: Add missing check for allocorderedworkqueue Add check for the return value of allocorderedworkqueue as it may return NULL pointer and cause NULL pointer dereference. Patchwork:...
CVE-2023-53223
The CVE-2023-53223 issue affects the Linux kernel component drm/msm/dsi where alloc_ordered_workqueue may return NULL. The vulnerability arises from a missing check of the return value, potentially leading to a NULL pointer dereference. A patch addressing this check has been published (Patchwork:...
CVE-2023-53223 drm/msm/dsi: Add missing check for alloc_ordered_workqueue
In the Linux kernel, the following vulnerability has been resolved: drm/msm/dsi: Add missing check for allocorderedworkqueue Add check for the return value of allocorderedworkqueue as it may return NULL pointer and cause NULL pointer dereference. Patchwork:...
CVE-2023-53223 drm/msm/dsi: Add missing check for alloc_ordered_workqueue
In the Linux kernel, the following vulnerability has been resolved: drm/msm/dsi: Add missing check for allocorderedworkqueue Add check for the return value of allocorderedworkqueue as it may return NULL pointer and cause NULL pointer dereference. Patchwork:...
PT-2025-37657
Name of the Vulnerable Software and Affected Versions: Linux kernel versions prior to 6.2.0-rc3-rt1 Description: A flaw exists in the Linux kernel related to the EFI runtime services. Specifically, the efi rt lock spinlock could lead to preemption issues when called from within EFI runtime...
PT-2025-37664
Name of the Vulnerable Software and Affected Versions: Linux kernel affected versions not specified Description: A missing check for the return value of alloc ordered workqueue can lead to a NULL pointer dereference within the drm/msm/dsi subsystem of the Linux kernel. The vulnerability is...
Linux kernel 安全漏洞
Linux kernel is the kernel used by Linux, the open source operating system of the Linux Foundation in the United States. A security vulnerability exists in Linux kernel that stems from an unchecked allocorderedworkqueue return value that could result in a null pointer dereference...
CVE-2025-39737
In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid soft lockup in kmemleakdocleanup A soft lockup warning was observed on a relative small system x86-64 system with 16 GB of memory when running a debug kernel with kmemleak enabled. watchdog: BUG: soft lockup -...
CVE-2025-39737
CVE-2025-39737 corresponds to a Linux kernel kmemleak issue where soft lockups occurred during cleanup of a large kmemleak object set (e.g., ~40k objects). The provided Astra Linux bulletin notes the fix: in kmemleak_do_cleanup(), periodically call cond_resched() inside the cleanup loop to avoid ...
CVE-2025-39737 mm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup()
In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid soft lockup in kmemleakdocleanup A soft lockup warning was observed on a relative small system x86-64 system with 16 GB of memory when running a debug kernel with kmemleak enabled. watchdog: BUG: soft lockup -...
CVE-2025-39737 mm/kmemleak: avoid soft lockup in __kmemleak_do_cleanup()
In the Linux kernel, the following vulnerability has been resolved: mm/kmemleak: avoid soft lockup in kmemleakdocleanup A soft lockup warning was observed on a relative small system x86-64 system with 16 GB of memory when running a debug kernel with kmemleak enabled. watchdog: BUG: soft lockup -...
PT-2025-44760
Name of the Vulnerable Software and Affected Versions Linux Kernel hi311x CAN driver affected versions not specified Description The Linux kernel’s hi311x CAN driver contains a flaw where a null pointer dereference can occur when resuming from sleep if the network interface was not previously...
kernel: drm/vkms: Fix null-ptr-deref in vkms_release()
In the Linux kernel, the following vulnerability has been resolved: drm/vkms: Fix null-ptr-deref in vkmsrelease A null-ptr-deref is triggered when it tries to destroy the workqueue in vkms-output.composerworkq in vkmsrelease. KASAN: null-ptr-deref in range 0x0000000000000118-0x000000000000011f CP...
SUSE CVE-2025-39692
In the Linux kernel, the following vulnerability has been resolved: smb: server: split ksmbdrdmastoplistening out of ksmbdrdmadestroy We can't call destroyworkqueuesmbdirectwq; before stopsessions! Otherwise already existing connections try to use smbdirectwq as a NULL pointer...
crypto: qat - flush misc workqueue during device shutdown
...
SUSE CVE-2025-39721
In the Linux kernel, the following vulnerability has been resolved: crypto: qat - flush misc workqueue during device shutdown Repeated loading and unloading of a device specific QAT driver, for example qat4xxx, in a tight loop can lead to a crash due to a use-after-free scenario. This occurs when...
CVE-2025-39721
In the Linux kernel, the following vulnerability has been resolved: crypto: qat - flush misc workqueue during device shutdown Repeated loading and unloading of a device specific QAT driver, for example qat4xxx, in a tight loop can lead to a crash due to a use-after-free scenario. This occurs when...