68552 matches found
CVE-2026-90091
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: fix race l2capsockcleanuplisten vs. putchan For L2CAP sockets without owning sk-sksocket, reading l2cappisk-chan may race against concurrent l2capsockkill - l2capsockputchan. This excludes simultaneous protoops...
DEBIAN-CVE-2026-90066
In the Linux kernel, the following vulnerability has been resolved: samples/ftrace: Fix kthreadstop on ERRPTR in ftrace-direct-multi-modify ftracedirectmultiinit assigns kthreadrun's return value to simpletsk without an ISERR check. When kthreadrun fails it returns ERRPTR-ENOMEM, but init still...
CVE-2022-34683
CVE-2022-34683 Windows용 NVIDIA GPU 디스플레이 드라이버에는 DxgkDdiEscape에 대한 커널 모드 레이어nvlddmkm.sys 핸들러에서 null 포인터 역참조가 발생하는 취약점이 포함되어 있으며, 이로 인해 서비스 거부가 발생할 수 있습니다. 인증| 복잡성| 벡터 ---|---|--- 해당 사항 없음| 해당 사항 없음| 해당 사항 없음...
CVE-2026-76781
A flaw was found in libxml2. A local user or an attacker providing a specially crafted XML catalog can trigger a NULL pointer dereference during XML catalog parsing. This occurs when a nextCatalog element lacks its mandatory catalog attribute, leading to the application crashing and causing a...
EUVD-2026-82288
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Fix NPD issue on partial unmap of an evicted BO This commit fixes the NULL pointer dereference issue that would have happened on the split of GPU mapping due to partial unmap of an evicted BO. There is a logic to...
CVE-2026-93180
CVE-2026-93180 affects the Linux kernel's drm/panthor GPU driver. A NULL pointer dereference occurs when a GPU memory mapping is split during a partial unmap of an evicted Buffer Object (BO) . The root cause is that the logic handling partial unmap of huge pages was not fully skipped for the VMA ...
CVE-2026-93139
CVE-2026-93139 affects the Linux kernel's amdgpu driver , specifically the MES (Micro-Engine Scheduler) component. The root cause is a loop in the hung_queue_db_array that iterated only AMDGPU_MAX_MES_PIPES times, leaving entries uninitialized for multi-XCC GPUs. This results in null pointer dere...
EUVD-2026-82247
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/mes: Fix hungqueuedbarray loop limit for multi-XCC The loop iterated only AMDGPUMAXMESPIPES times, leaving entries uninitialized for multi-XCC GPUs. This causes null pointer dereferences when accessing arrays indexed b...
EUVD-2026-82232
In the Linux kernel, the following vulnerability has been resolved: platform/x86: asus-wireless: Fail probe when there is no ACPI match Every platform driver can be forced to match a device that does not match its list of device IDs because of devicematchdriveroverride, so platform drivers that...
CVE-2026-93124
CVE-2026-93124 affects the asus-wireless platform/x86 driver in the Linux kernel . The root cause is that asus_wireless_probe() returns success even when acpi_match_acpi_device() finds no match, storing a NULL companion pointer . When the driver is force-bound to a device without an ACPI companio...
EUVD-2026-82226
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: aspeedudc: check endpoint DMA allocation astudcprobe allocates a coherent DMA buffer used as the backing store for endpoint buffers. astudcinitep derives per-endpoint buffer pointers from udc-ep0buf, so a failed...
CVE-2026-93115
CVE-2026-93115 affects the Linux kernel 's platform/mellanox: mlxbf-pmc driver. The root cause is a NULL pointer dereference : mlxbf_pmc_probe() passes the result of ACPI_COMPANION() to acpi_device_hid(), which dereferences it. Because any platform driver can be force-bound to a device outside it...
EUVD-2026-82223
In the Linux kernel, the following vulnerability has been resolved: platform/mellanox: mlxbf-pmc: Check ACPICOMPANION against NULL Every platform driver can be forced to match a device that doesn't match its list of device IDs because of devicematchdriveroverride, so platform drivers that rely on...
CVE-2026-93114
CVE-2026-93114 affects the Linux kernel's platform/surface: acpi-notify driver. The root cause is a NULL pointer dereference in san_probe(), which dereferences the result of ACPI_COMPANION() when installing the GSBUS address space handler without verifying its presence. This flaw was introduced w...
EUVD-2026-82222
In the Linux kernel, the following vulnerability has been resolved: platform/surface: acpi-notify: Check ACPI companion before use Since every platform driver can be forced to match a device that doesn't match its list of device IDs because of devicematchdriveroverride, platform drivers that rely...
CVE-2026-93114 platform/surface: acpi-notify: Check ACPI companion before use
In the Linux kernel, the following vulnerability has been resolved: platform/surface: acpi-notify: Check ACPI companion before use Since every platform driver can be forced to match a device that doesn't match its list of device IDs because of devicematchdriveroverride, platform drivers that rely...
CVE-2026-93107 RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state
In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state When docomplete finds the QP in the error state it returns RESPSTCHKRESOURCE. Before commit 49dc9c1f0c7e "RDMA/rxe: Cleanup reset state handling ...
CVE-2026-93107
CVE-2026-93107 affects the Linux kernel RDMA/rxe (Soft-RoCE) subsystem. The root cause is a regression from commit 49dc9c1f0c7e, which removed the error-state branch from check_resource() but retained the error-state return in do_complete(). When a QP enters the error state while a packet is bein...
EUVD-2026-82215
In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Avoid reprocessing the current packet after the QP enters the error state When docomplete finds the QP in the error state it returns RESPSTCHKRESOURCE. Before commit 49dc9c1f0c7e "RDMA/rxe: Cleanup reset state handling ...
EUVD-2026-82183
In the Linux kernel, the following vulnerability has been resolved: dax: read holderops once in daxholdernotifyfailure daxholdernotifyfailure reads daxdev-holderops twice without READONCE -- once for the NULL check and once for the indirect notifyfailure call. A concurrent fsputdax can clear...