2993 matches found
CVE-2026-68106
A flaw was found in the Linux kernel's drm/amdgpu component. This vulnerability occurs when processing video frames with invalid dimensions, specifically if the width or height is less than 16. Such malformed input can lead to a division by zero error during video decoding operations. A local...
CVE-2026-68164
A flaw was found in the Linux kernel's DAMON Data Access MONitor subsystem. The damonsetregions function, responsible for setting memory monitoring regions, incorrectly processes unsorted or overlapping input ranges due to a missing validation check. This can lead to unexpected behavior in DAMON...
CVE-2026-68254
A flaw was found in the Linux kernel's drm/i915/vrr component. An attacker could provide a specially crafted Extended Display Identification Data EDID with a zero minimum vertical refresh rate minvfreq. This could lead to a division-by-zero error in the intelvrrcomputevmax function, resulting in ...
CVE-2026-68356
A flaw was found in the Linux kernel's airoha watchdog driver. This vulnerability occurs when the clock frequency is zero, causing the driver to attempt a division by zero. This can lead to a system crash, resulting in a denial of service for the affected system...
CVE-2026-68297
A flaw was found in the Linux kernel's TIPC Transparent Inter-Process Communication module. A local user can exploit this vulnerability by providing a crafted Maximum Transmission Unit MTU value that exceeds the expected limit. This can lead to a division-by-zero error, causing a system crash and...
CVE-2026-68356
In the Linux kernel, the following vulnerability has been resolved: watchdog: airoha: Prevent division by zero when clock frequency is zero clkgetrate can return 0 when the clock provider is not properly configured or the clock is unmanaged. The driver uses wdtfreq as a divisor directly in...
DEBIAN-CVE-2026-68356
In the Linux kernel, the following vulnerability has been resolved: watchdog: airoha: Prevent division by zero when clock frequency is zero clkgetrate can return 0 when the clock provider is not properly configured or the clock is unmanaged. The driver uses wdtfreq as a divisor directly in...
CVE-2026-68297
In the Linux kernel, the following vulnerability has been resolved: tipc: fix u16 MTU truncation in media and bearer MTU validation Both TIPCNLMEDIASET and TIPCNLBEARERSET accept user-supplied MTU values but only enforce a minimum bound, not a maximum. When a user sets the MTU to a value exceedin...
CVE-2026-68254
In the Linux kernel, the following vulnerability has been resolved: drm/i915/vrr: require valid min/max vfreq for VRR Ensure the EDID provided min/max vfreq are valid. Most scenarios are already covered by coincidence through the checks in intelvrriscapable and intelvrrisinrange, but be more...
DEBIAN-CVE-2026-68254
In the Linux kernel, the following vulnerability has been resolved: drm/i915/vrr: require valid min/max vfreq for VRR Ensure the EDID provided min/max vfreq are valid. Most scenarios are already covered by coincidence through the checks in intelvrriscapable and intelvrrisinrange, but be more...
CVE-2026-68164
In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: disallow overlapping input ranges for damonsetregions damonsetregions assumes the input ranges are sorted by the address and don't overlap each other. Hence the assumption was initially to be explicitly validated...
DEBIAN-CVE-2026-68164
In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: disallow overlapping input ranges for damonsetregions damonsetregions assumes the input ranges are sorted by the address and don't overlap each other. Hence the assumption was initially to be explicitly validated...
UBUNTU-CVE-2026-68356
In the Linux kernel, the following vulnerability has been resolved: watchdog: airoha: Prevent division by zero when clock frequency is zero clkgetrate can return 0 when the clock provider is not properly configured or the clock is unmanaged. The driver uses wdtfreq as a divisor directly in...
UBUNTU-CVE-2026-68254
In the Linux kernel, the following vulnerability has been resolved: drm/i915/vrr: require valid min/max vfreq for VRR Ensure the EDID provided min/max vfreq are valid. Most scenarios are already covered by coincidence through the checks in intelvrriscapable and intelvrrisinrange, but be more...
CVE-2026-68356
In the Linux kernel, the following vulnerability has been resolved: watchdog: airoha: Prevent division by zero when clock frequency is zero clkgetrate can return 0 when the clock provider is not properly configured or the clock is unmanaged. The driver uses wdtfreq as a divisor directly in...
CVE-2026-68297
In the Linux kernel, the following vulnerability has been resolved: tipc: fix u16 MTU truncation in media and bearer MTU validation Both TIPCNLMEDIASET and TIPCNLBEARERSET accept user-supplied MTU values but only enforce a minimum bound, not a maximum. When a user sets the MTU to a value exceedin...
CVE-2026-68164
In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: disallow overlapping input ranges for damonsetregions damonsetregions assumes the input ranges are sorted by the address and don't overlap each other. Hence the assumption was initially to be explicitly validated...
UBUNTU-CVE-2026-68297
In the Linux kernel, the following vulnerability has been resolved: tipc: fix u16 MTU truncation in media and bearer MTU validation Both TIPCNLMEDIASET and TIPCNLBEARERSET accept user-supplied MTU values but only enforce a minimum bound, not a maximum. When a user sets the MTU to a value exceedin...
CVE-2026-68254
In the Linux kernel, the following vulnerability has been resolved: drm/i915/vrr: require valid min/max vfreq for VRR Ensure the EDID provided min/max vfreq are valid. Most scenarios are already covered by coincidence through the checks in intelvrriscapable and intelvrrisinrange, but be more...
CVE-2026-68106
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix division by zero with invalid uvd dimensions When width or height is less than 16, widthinmb or heightinmb becomes 0, leading to fsinmb being 0. This causes a division by zero when calculating numdpbbuffer in H264...