rpm package
opensuse/kernel-source&distro=openSUSE Leap 16.1
pkg:rpm/opensuse/kernel-source&distro=openSUSE%20Leap%2016.1
Vulnerabilities (2,819)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-72126 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: can: isotp: use unconditional synchronize_rcu() in isotp_release() isotp_notify() unregisters the (RCU) CAN filters via can_rx_unregister() and clears so->bound without waiting for a grace period. isotp_release | |
| CVE-2026-72123 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: can: bcm: defer rx_op deallocation to workqueue to fix thrtimer UAF Commit f1b4e32aca08 ("can: bcm: use call_rcu() instead of costly synchronize_rcu()") replaced synchronize_rcu() in bcm_delete_rx_op() with cal | |
| CVE-2026-72122 | Hig | 7.3 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: can: bcm: fix lockless bound/ifindex race and silent RX_SETUP failure bcm_sendmsg() reads bo->ifindex and checks bo->bound before taking lock_sock(), while bcm_notify(), bcm_connect() and bcm_release() all muta | |
| CVE-2026-72120 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: can: bcm: add missing rcu list annotations and operations sashiko-bot remarked the missing use of list_add_rcu() in bcm_[rx|tx]_setup() to have a proper initialized bcm_op structure when bcm_proc_show() travers | |
| CVE-2026-72111 | Hig | 8.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: bpf: Reset register bounds before narrowing retval range in check_mem_access() When the BPF verifier processes a context load of an LSM hook return value, it calls __mark_reg_s32_range() to narrow the register | |
| CVE-2026-72110 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: bpf,fork: wipe ->bpf_storage before bailouts that access it Currently, copy_process() can bail out to free_task() before p->bpf_storage has been initialized, with this call graph (shown here for the !CONFIG_MEM | |
| CVE-2026-72108 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: dm thin metadata: fix metadata snapshot consistency on commit failure __reserve_metadata_snap() and __release_metadata_snap() modify the superblock's held_root directly in the block_manager's buffer. If the sub | |
| CVE-2026-72107 | Hig | 8.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: dm era: fix out-of-bounds memory access for non-zero start sector dm-era tracks writes in target-relative blocks, but era_map() calculates the writeset block before applying the target offset. Tables with a no | |
| CVE-2026-72106 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: dm-ioctl: fix a possible overflow in list_version_get_info sizeof(tt->version) is 12 bytes, but the code writes 16 bytes into the output buffer - info->vers->version[0], info->vers->version[1], info->vers->vers | ||
| CVE-2026-72105 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: dm-log: fix a bitset_size overflow on 32bit machines Commit c20e36b7631d ("dm log: fix out-of-bounds write due to region_count overflow") made sure that region_count could fit in an unsigned int. But the bitmap | |
| CVE-2026-72103 | Hig | 7.3 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: dm: avoid leaking the caller's thread keyring via the table device file The refactoring in commit a28d893eb327 ("md: port block device access to file") accidentally causes the caller's thread keyring to be kept | |
| CVE-2026-72102 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: dm_early_create: fix freeing used table on dm_resume failure If dm_resume fails, the kernel attempts to free table with dm_table_destroy, but the table was already instantiated with dm_swap_table. This commit s | |
| CVE-2026-72101 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix leaking uninitialized kernel memory If hash size is less than device's tuple size, dm-integrity is supposed to zero the remaining space. There was a bug in the code that zeroing didn't work. T | ||
| CVE-2026-72100 | Hig | 8.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix a bug if the bio is out of limits If dm_integrity_check_limits fails, the code would exit with DM_MAPIO_KILL. However, the range would be already locked at this point, and it wouldn't be unloc | |
| CVE-2026-72098 | Cri | 9.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: dm-verity: fix buffer overflow in FEC calculation There's a buffer overflow in dm-verity-fec: if (neras && *neras <= v->fec->roots) fio->erasures[(*neras)++] = i; This allows *neras to reach roots + 1 (the p | |
| CVE-2026-72095 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: dma-fence: Make dma_fence_dedup_array() robust against 0-count input dma_fence_dedup_array() returns 1 when called with num_fences == 0: the for-loop body never executes, j stays at 0, and the final `return ++j | |
| CVE-2026-72093 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: accel/amdxdna: Fix use-after-free in amdxdna_gem_dmabuf_mmap() When vm_insert_pages() fails, the error path calls vma->vm_ops->close(vma) which internally calls drm_gem_vm_close() → drm_gem_object_put(), releas | |
| CVE-2026-72092 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: accel/amdxdna: reject command submission on devices without a submit op amdxdna_cmd_submit() calls xdna->dev_info->ops->cmd_submit() unconditionally, but only aie2_dev_ops defines that callback. aie4_vf_ops (th | ||
| CVE-2026-72091 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: accel/amdxdna: reject user command submission without a command BO amdxdna_drm_submit_execbuf() passes the user-supplied command BO handle straight into amdxdna_cmd_submit() with drv_cmd == NULL. When the handl | ||
| CVE-2026-72089 | Hig | 7.1 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 15, 2026 | In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Reject firmware log with size smaller than header fw_log_from_bo() validates the tracing buffer header_size and that the log fits within the BO, but never checks that log->size is at least log->head |
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: can: isotp: use unconditional synchronize_rcu() in isotp_release() isotp_notify() unregisters the (RCU) CAN filters via can_rx_unregister() and clears so->bound without waiting for a grace period. isotp_release
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: can: bcm: defer rx_op deallocation to workqueue to fix thrtimer UAF Commit f1b4e32aca08 ("can: bcm: use call_rcu() instead of costly synchronize_rcu()") replaced synchronize_rcu() in bcm_delete_rx_op() with cal
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: can: bcm: fix lockless bound/ifindex race and silent RX_SETUP failure bcm_sendmsg() reads bo->ifindex and checks bo->bound before taking lock_sock(), while bcm_notify(), bcm_connect() and bcm_release() all muta
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: can: bcm: add missing rcu list annotations and operations sashiko-bot remarked the missing use of list_add_rcu() in bcm_[rx|tx]_setup() to have a proper initialized bcm_op structure when bcm_proc_show() travers
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: bpf: Reset register bounds before narrowing retval range in check_mem_access() When the BPF verifier processes a context load of an LSM hook return value, it calls __mark_reg_s32_range() to narrow the register
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: bpf,fork: wipe ->bpf_storage before bailouts that access it Currently, copy_process() can bail out to free_task() before p->bpf_storage has been initialized, with this call graph (shown here for the !CONFIG_MEM
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: dm thin metadata: fix metadata snapshot consistency on commit failure __reserve_metadata_snap() and __release_metadata_snap() modify the superblock's held_root directly in the block_manager's buffer. If the sub
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: dm era: fix out-of-bounds memory access for non-zero start sector dm-era tracks writes in target-relative blocks, but era_map() calculates the writeset block before applying the target offset. Tables with a no
- CVE-2026-72106Aug 15, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: dm-ioctl: fix a possible overflow in list_version_get_info sizeof(tt->version) is 12 bytes, but the code writes 16 bytes into the output buffer - info->vers->version[0], info->vers->version[1], info->vers->vers
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: dm-log: fix a bitset_size overflow on 32bit machines Commit c20e36b7631d ("dm log: fix out-of-bounds write due to region_count overflow") made sure that region_count could fit in an unsigned int. But the bitmap
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: dm: avoid leaking the caller's thread keyring via the table device file The refactoring in commit a28d893eb327 ("md: port block device access to file") accidentally causes the caller's thread keyring to be kept
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: dm_early_create: fix freeing used table on dm_resume failure If dm_resume fails, the kernel attempts to free table with dm_table_destroy, but the table was already instantiated with dm_swap_table. This commit s
- CVE-2026-72101Aug 15, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix leaking uninitialized kernel memory If hash size is less than device's tuple size, dm-integrity is supposed to zero the remaining space. There was a bug in the code that zeroing didn't work. T
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: dm-integrity: fix a bug if the bio is out of limits If dm_integrity_check_limits fails, the code would exit with DM_MAPIO_KILL. However, the range would be already locked at this point, and it wouldn't be unloc
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: dm-verity: fix buffer overflow in FEC calculation There's a buffer overflow in dm-verity-fec: if (neras && *neras <= v->fec->roots) fio->erasures[(*neras)++] = i; This allows *neras to reach roots + 1 (the p
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: dma-fence: Make dma_fence_dedup_array() robust against 0-count input dma_fence_dedup_array() returns 1 when called with num_fences == 0: the for-loop body never executes, j stays at 0, and the final `return ++j
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: accel/amdxdna: Fix use-after-free in amdxdna_gem_dmabuf_mmap() When vm_insert_pages() fails, the error path calls vma->vm_ops->close(vma) which internally calls drm_gem_vm_close() → drm_gem_object_put(), releas
- CVE-2026-72092Aug 15, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: accel/amdxdna: reject command submission on devices without a submit op amdxdna_cmd_submit() calls xdna->dev_info->ops->cmd_submit() unconditionally, but only aie2_dev_ops defines that callback. aie4_vf_ops (th
- CVE-2026-72091Aug 15, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: accel/amdxdna: reject user command submission without a command BO amdxdna_drm_submit_execbuf() passes the user-supplied command BO handle straight into amdxdna_cmd_submit() with drv_cmd == NULL. When the handl
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Reject firmware log with size smaller than header fw_log_from_bo() validates the tracing buffer header_size and that the log fits within the BO, but never checks that log->size is at least log->head
Page 100 of 141