rpm package
opensuse/kernel-docs&distro=openSUSE Leap 16.1
pkg:rpm/opensuse/kernel-docs&distro=openSUSE%20Leap%2016.1
Vulnerabilities (2,819)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-89820 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fix dc_lock leak on GPU reset error paths On GPU reset, dm_suspend() takes dc_lock and leaves it for dm_resume() to drop. If amdgpu_dm_commit_zero_streams() or dm_dmub_hw_init() fails, the func | ||
| CVE-2026-89819 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: validate plane degamma LUT size for private color prop Unlike the CRTC degamma path, which is guarded by amdgpu_dm_verify_lut_sizes(), the per-plane degamma LUT size was never validated before | |
| CVE-2026-89818 | Hig | 7.1 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vcn: fix integer overflow in dec_msg buffer count check If the supplied msg[2] (num_buffers) is 0x3FFFFFFF, the expression 6 + num_buffers * 4 wraps to 2 and the bounds check passes, letting the pars | |
| CVE-2026-89817 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/gud: NUL-terminate TV mode names read from the device gud_connector_add_tv_mode() reads a buffer of fixed-size mode names from the USB device and passes pointers into it to drm_mode_create_tv_properties_leg | ||
| CVE-2026-89816 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used Commit 1c6ceeee6ebb ("drm/atomic: Fix memleak on ERESTARTSYS during non-blocking commits") fixed a very similar issue when the event was al | ||
| CVE-2026-89815 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/ttm: Drop tt->restore after successful restore ttm_pool_restore_and_alloc() can successfully complete the restore process via ttm_pool_restore_commit(), but tt->restore is not dropped afterward. As a result | |
| CVE-2026-89814 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: clamp the isolation index for rings outside a partition adev->isolation[] has one slot per partition, but a ring that is not assigned to one keeps AMDGPU_XCP_NO_PARTITION, which is ~0, so indexing t | |
| CVE-2026-89813 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: force complete the KIQ ring fences on reset Like the MES scheduler ring, the KIQ ring sets no_scheduler = true and uses a polling fence, so it is skipped by the force-completion loop in amdgpu_devic | ||
| CVE-2026-89812 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: force complete the MES ring fences on reset The MES scheduler ring has no drm scheduler (no_scheduler = true), so it is skipped by the force-completion loop in amdgpu_device_pre_asic_reset(). It use | ||
| CVE-2026-89811 | Hig | 8.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Add TLB flush after MES queue eviction/suspension MES (Micro Engine Scheduler) does not perform heavy-weight TLB invalidation after unmapping queues, unlike HWS which does this automatically. This c | |
| CVE-2026-89807 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: guard against NULL restore_mqd in CRIU queue restore Both create_queue_cpsch() and create_queue_nocpsch() unconditionally call mqd_mgr->restore_mqd() when a CRIU restore is in progress (qd != NULL), | ||
| CVE-2026-89806 | Hig | 8.4 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/sysfb: ofdrm: Fix integer overflow in fb_size calculation The framebuffer size calculation `fb_size = linebytes * height` can overflow when both values are large (e.g., 46341 * 46341 > INT_MAX). Since lineb | |
| CVE-2026-89803 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: unsubscribe the channel-kill event before the fence context nouveau_channel_del() tears the fence context down first and only drops the channel-kill subscription later, in the middle of the nvif ob | |
| CVE-2026-89802 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/uvmm: fix NULL deref unwinding an OP_MAP_SPARSE op Each bind_job_op is zeroed by kzalloc_obj() in bind_job_op_from_uop(), and the OP_MAP_SPARSE case in nouveau_uvmm_bind_job_submit() only creates a | ||
| CVE-2026-89801 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE In nouveau_uvmm_bind_job_submit()'s OP_UNMAP_SPARSE arm, op->reg is set from nouveau_uvma_region_find(), which only looks the region up and | |
| CVE-2026-89800 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE A successful OP_UNMAP_SPARSE marks its region dirty with nouveau_uvma_region_dirty() and defers the teardown to nouveau_uvmm_bind_job_cle | ||
| CVE-2026-89798 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: rpcrdma: arm rn_done before publishing the notification rpcrdma_rn_register() inserts @rn into rd_xa with xa_alloc() before storing the caller's callback in rn->rn_done. The xarray makes @rn reachable to rpcrdm | ||
| CVE-2026-89797 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: power: supply: ab8500_fg: fix use-after-free on remove ab8500_fg_remove() destroys the driver workqueue while the threaded interrupt handlers are still armed; they are devm-managed and freed only after ->remove | ||
| CVE-2026-89791 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: perf: Fix use-after-free when perf mmap() revival races with the last munmap() perf_mmap_close() drops rb->mmap_count *without* holding event->mmap_mutex (the refcount_dec_and_test() right before the refcount_d | |
| CVE-2026-89789 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 16, 2026 | In the Linux kernel, the following vulnerability has been resolved: gtp: add synchronize_net() in gtp_newlink() error path to prevent use-after-free gtp_newlink()'s error path frees tid_hash and addr_hash without waiting for an RCU grace period after clearing sk_user_data. A co |
- CVE-2026-89820Sep 16, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: fix dc_lock leak on GPU reset error paths On GPU reset, dm_suspend() takes dc_lock and leaves it for dm_resume() to drop. If amdgpu_dm_commit_zero_streams() or dm_dmub_hw_init() fails, the func
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: validate plane degamma LUT size for private color prop Unlike the CRTC degamma path, which is guarded by amdgpu_dm_verify_lut_sizes(), the per-plane degamma LUT size was never validated before
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vcn: fix integer overflow in dec_msg buffer count check If the supplied msg[2] (num_buffers) is 0x3FFFFFFF, the expression 6 + num_buffers * 4 wraps to 2 and the bounds check passes, letting the pars
- CVE-2026-89817Sep 16, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/gud: NUL-terminate TV mode names read from the device gud_connector_add_tv_mode() reads a buffer of fixed-size mode names from the USB device and passes pointers into it to drm_mode_create_tv_properties_leg
- CVE-2026-89816Sep 16, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used Commit 1c6ceeee6ebb ("drm/atomic: Fix memleak on ERESTARTSYS during non-blocking commits") fixed a very similar issue when the event was al
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/ttm: Drop tt->restore after successful restore ttm_pool_restore_and_alloc() can successfully complete the restore process via ttm_pool_restore_commit(), but tt->restore is not dropped afterward. As a result
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: clamp the isolation index for rings outside a partition adev->isolation[] has one slot per partition, but a ring that is not assigned to one keeps AMDGPU_XCP_NO_PARTITION, which is ~0, so indexing t
- CVE-2026-89813Sep 16, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: force complete the KIQ ring fences on reset Like the MES scheduler ring, the KIQ ring sets no_scheduler = true and uses a polling fence, so it is skipped by the force-completion loop in amdgpu_devic
- CVE-2026-89812Sep 16, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: force complete the MES ring fences on reset The MES scheduler ring has no drm scheduler (no_scheduler = true), so it is skipped by the force-completion loop in amdgpu_device_pre_asic_reset(). It use
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Add TLB flush after MES queue eviction/suspension MES (Micro Engine Scheduler) does not perform heavy-weight TLB invalidation after unmapping queues, unlike HWS which does this automatically. This c
- CVE-2026-89807Sep 16, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: guard against NULL restore_mqd in CRIU queue restore Both create_queue_cpsch() and create_queue_nocpsch() unconditionally call mqd_mgr->restore_mqd() when a CRIU restore is in progress (qd != NULL),
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/sysfb: ofdrm: Fix integer overflow in fb_size calculation The framebuffer size calculation `fb_size = linebytes * height` can overflow when both values are large (e.g., 46341 * 46341 > INT_MAX). Since lineb
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: unsubscribe the channel-kill event before the fence context nouveau_channel_del() tears the fence context down first and only drops the channel-kill subscription later, in the middle of the nvif ob
- CVE-2026-89802Sep 16, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/uvmm: fix NULL deref unwinding an OP_MAP_SPARSE op Each bind_job_op is zeroed by kzalloc_obj() in bind_job_op_from_uop(), and the OP_MAP_SPARSE case in nouveau_uvmm_bind_job_submit() only creates a
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE In nouveau_uvmm_bind_job_submit()'s OP_UNMAP_SPARSE arm, op->reg is set from nouveau_uvma_region_find(), which only looks the region up and
- CVE-2026-89800Sep 16, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE A successful OP_UNMAP_SPARSE marks its region dirty with nouveau_uvma_region_dirty() and defers the teardown to nouveau_uvmm_bind_job_cle
- CVE-2026-89798Sep 16, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: rpcrdma: arm rn_done before publishing the notification rpcrdma_rn_register() inserts @rn into rd_xa with xa_alloc() before storing the caller's callback in rn->rn_done. The xarray makes @rn reachable to rpcrdm
- CVE-2026-89797Sep 16, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: power: supply: ab8500_fg: fix use-after-free on remove ab8500_fg_remove() destroys the driver workqueue while the threaded interrupt handlers are still armed; they are devm-managed and freed only after ->remove
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: perf: Fix use-after-free when perf mmap() revival races with the last munmap() perf_mmap_close() drops rb->mmap_count *without* holding event->mmap_mutex (the refcount_dec_and_test() right before the refcount_d
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: gtp: add synchronize_net() in gtp_newlink() error path to prevent use-after-free gtp_newlink()'s error path frees tid_hash and addr_hash without waiting for an RCU grace period after clearing sk_user_data. A co
Page 52 of 141