Page 200 of 4393 results (0.018 seconds)

CVSS: -EPSS: 0%CPEs: 7EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry In a review discussion of the changes to support vCPU hotplug where a check was added on the GICC being enabled if was online, it was noted that there is need to map back to the cpu and use that to index into a cpumask. As such, a valid ID is needed. If an MPIDR check fails in acpi_map_gic_cpu_interface() it is possible for the entry in cpu_madt_gicc[cpu] == NULL. This function would then cause a NULL pointer dereference. Whilst a path to trigger this has not been established, harden this caller against the possibility. • https://git.kernel.org/stable/c/f57769ff6fa7f97f1296965f20e8a2bb3ee9fd0f https://git.kernel.org/stable/c/4c3b21204abb4fa3ab310fbbb5cf7f0e85f3a1bc https://git.kernel.org/stable/c/945be49f4e832a9184c313fdf8917475438a795b https://git.kernel.org/stable/c/40cae0df42e5e7f7a1c0f32deed9c4027c1ba94e https://git.kernel.org/stable/c/62ca6d3a905b4c40cd942f3cc645a6718f8bc7e7 https://git.kernel.org/stable/c/bc7fbb37e3d2df59336eadbd6a56be632e3c7df7 https://git.kernel.org/stable/c/2488444274c70038eb6b686cba5f1ce48ebb9cdd •

CVSS: -EPSS: 0%CPEs: 4EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: drm/amd/pm: Fix negative array index read Avoid using the negative values for clk_idex as an index into an array pptable->DpmDescriptor. V2: fix clk_index return check (Tim Huang) • https://git.kernel.org/stable/c/60f4a4bc3329e5cb8c4df0cc961f0d5ffd96e22d https://git.kernel.org/stable/c/4711b1347cb9f0c3083da6d87c624d75f9bd1d50 https://git.kernel.org/stable/c/06a3810010b525b9958424e344f0c25b09e128fa https://git.kernel.org/stable/c/c8c19ebf7c0b202a6a2d37a52ca112432723db5f •

CVSS: -EPSS: 0%CPEs: 2EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vcn: remove irq disabling in vcn 5 suspend We do not directly enable/disable VCN IRQ in vcn 5.0.0. And we do not handle the IRQ state as well. So the calls to disable IRQ and set state are removed. This effectively gets rid of the warining of "WARN_ON(!amdgpu_irq_enabled(adev, src, type))" in amdgpu_irq_put(). • https://git.kernel.org/stable/c/aa92264ba6fd4fb570002f69762634221316e7ae https://git.kernel.org/stable/c/10fe1a79cd1bff3048e13120e93c02f8ecd05e9d •

CVSS: -EPSS: 0%CPEs: 6EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: the warning dereferencing obj for nbio_v7_4 if ras_manager obj null, don't print NBIO err data • https://git.kernel.org/stable/c/614564a5b28983de53b23a358ebe6c483a2aa21e https://git.kernel.org/stable/c/d04ded1e73f1dcf19a71ec8b9cda3faa7acd8828 https://git.kernel.org/stable/c/70e8ec21fcb8c51446899d3bfe416b31adfa3661 https://git.kernel.org/stable/c/7d265772e44d403071a2b573eac0db60250b1c21 https://git.kernel.org/stable/c/130c2dc75c8c40acc3c96ededea6af80e03c14b8 https://git.kernel.org/stable/c/d190b459b2a4304307c3468ed97477b808381011 •

CVSS: -EPSS: 0%CPEs: 7EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check gpio_id before used as array index [WHY & HOW] GPIO_ID_UNKNOWN (-1) is not a valid value for array index and therefore should be checked in advance. This fixes 5 OVERRUN issues reported by Coverity. • https://git.kernel.org/stable/c/8520fdc8ecc38f240a8e9e7af89cca6739c3e790 https://git.kernel.org/stable/c/40c2e8bc117cab8bca8814735f28a8b121654a84 https://git.kernel.org/stable/c/0184cca30cad74d88f5c875d4e26999e26325700 https://git.kernel.org/stable/c/276e3fd93e3beb5894eb1cc8480f9f417d51524d https://git.kernel.org/stable/c/08e7755f754e3d2cef7d3a7da538d33526bd6f7c https://git.kernel.org/stable/c/3d4198ab612ad48f73383ad3bb5663e6f0cdf406 https://git.kernel.org/stable/c/2a5626eeb3b5eec7a36886f9556113dd93ec8ed6 •