13 matches found
DEBIAN-CVE-2026-99090
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: serialize vblank counter reads against GPU reset The vblank counter callback reads display registers and scanout position without holding resetdomain-sem. During GPU recovery, display commit work can call the callback...
CVE-2026-99090
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: serialize vblank counter reads against GPU reset The vblank counter callback reads display registers and scanout position without holding resetdomain-sem. During GPU recovery, display commit work can call the callback...
EUVD-2026-109896
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: serialize vblank counter reads against GPU reset The vblank counter callback reads display registers and scanout position without holding resetdomain-sem. During GPU recovery, display commit work can call the callback...
CVE-2026-99090 drm/amdgpu: serialize vblank counter reads against GPU reset
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: serialize vblank counter reads against GPU reset The vblank counter callback reads display registers and scanout position without holding resetdomain-sem. During GPU recovery, display commit work can call the callback...
SUSE CVE-2026-97514
In the Linux kernel, the following vulnerability has been resolved: media: chips-media: wave5: Fix Reports from Kernel Lock Validator handledynamicresolution change requires that the statelock be acquired based on the lockdepassertheld. However, the handledynamicresolutionchange call in...
AZL-103622 CVE-2026-97514 affecting package kernel 6.6.157.1-1
In the Linux kernel, the following vulnerability has been resolved: media: chips-media: wave5: Fix Reports from Kernel Lock Validator handledynamicresolution change requires that the statelock be acquired based on the lockdepassertheld. However, the handledynamicresolutionchange call in...
UBUNTU-CVE-2026-97514
In the Linux kernel, the following vulnerability has been resolved: media: chips-media: wave5: Fix Reports from Kernel Lock Validator handledynamicresolution change requires that the statelock be acquired based on the lockdepassertheld. However, the handledynamicresolutionchange call in...
CVE-2026-97514 media: chips-media: wave5: Fix Reports from Kernel Lock Validator
In the Linux kernel, the following vulnerability has been resolved: media: chips-media: wave5: Fix Reports from Kernel Lock Validator handledynamicresolution change requires that the statelock be acquired based on the lockdepassertheld. However, the handledynamicresolutionchange call in...
CVE-2026-97514
The Linux kernel contains a vulnerability within the chips-media: wave5 media driver. The issue stems from the handle_dynamic_resolution_change call in initialize_sequence, which fails to properly acquire the state_lock before execution, triggering reports from the Kernel Lock Validator . Because...
CVE-2026-97514
In the Linux kernel, the following vulnerability has been resolved: media: chips-media: wave5: Fix Reports from Kernel Lock Validator handledynamicresolution change requires that the statelock be acquired based on the lockdepassertheld. However, the handledynamicresolutionchange call in...
CVE-2026-97514: Undefined Security Weakness
In the Linux kernel, the following vulnerability has been resolved: media: chips-media: wave5: Fix Reports from Kernel Lock Validator handledynamicresolution change requires that the statelock be acquired based on the lockdepassertheld. However, the handledynamicresolutionchange call in...
CVE-2024-36000
In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix missing hugetlblock for resv uncharge There is a recent report on UFFDIOCOPY over hugetlb: https://lore.kernel.org/all/[email protected]/ 350: lockdepassertheld&hugetlblock; Should be an issu...
CVE-2024-36000
The vulnerability CVE-2024-36000 is a Linux kernel issue where mm/hugetlb could miss acquiring hugetlb_lock during resv uncharge, particularly in a userfault context via UFFDIO_COPY. The root cause is locking criteria being overlooked in hugetlb_cgroup_uncharge_folio_rsvd(), which updates the cgr...