rpm package
opensuse/dtb-aarch64&distro=openSUSE Leap 16.1
pkg:rpm/opensuse/dtb-aarch64&distro=openSUSE%20Leap%2016.1
Vulnerabilities (2,819)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-80709 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: s390/zcrypt: Fix wrong domain value verification with EP11 CPRBs There is a wrong upper limit check for the domain value when an EP11 CPRB is processed for sending to a crypto card. This check is only active on | |
| CVE-2026-80707 | Hig | 7.5 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: can: j1939: transport: j1939_session_fresh_new(): initialize receive buffer Zero the allocated buffer in j1939_session_fresh_new() to ensure it contains no residual data. While there is a potential performance | |
| CVE-2026-80706 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: can: softing: fw_parse(): validate firmware record spans fw_parse() reads a fixed record header, a firmware-provided payload, and a trailing checksum without knowing the end of the firmware blob. A truncated re | |
| CVE-2026-80704 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: use proper context for logging The same as the rest of the code, get_ss_info_from_atombios() uses calc_pll_cs->ctx->logger for logging. But calc_pll_cs->ctx is initialized only later in calc_pl | ||
| CVE-2026-80703 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix missing authorization check in KFD_IOC_DBG_TRAP_DISABLE Prevent unauthorized termination of active GPU debug sessions. Previously, users with /dev/kfd access could terminate another process's de | ||
| CVE-2026-80702 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: fix guest_memory_dirty bitfield clobbered as size Two sites in vmwgfx_resource.c assign boolean literals to res->guest_memory_size, which is an unsigned long allocation-size field; the intended targ | |
| CVE-2026-80701 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: enforce cursor size limits for MOB cursors vmw_cursor_plane_atomic_check() bounds cursor width and height only on the legacy update path; the SVGA_CAP2_CURSOR_MOB path -- the default on modern hosts | ||
| CVE-2026-80700 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: validate external BO copy bounds for both stride paths vmw_external_bo_copy() trusts caller-supplied offsets, strides, and heights and operates on imported dma-buf vmaps: - The equal-stride memcp | |
| CVE-2026-80698 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: fix double free of wq, engine, and group structs The release callbacks for wq, engine, and group devices (idxd_conf_wq_release, idxd_conf_engine_release, idxd_conf_group_release) each call kfre | ||
| CVE-2026-80696 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: hwmon: (ltc4282) Fix reading the minimum alarm voltage Coverity reports an out-of-bounds access when reading the minimum alarm voltage for the VGPIO channel. Add the missing return statement to fix the problem. | |
| CVE-2026-80695 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: hwmon: (sht3x) Fix unaligned accesses Sashiko reports: In sht3x_update_client(), the 16-bit temperature and humidity values are extracted from a stack-allocated byte array using be16_to_cpup(). The pointers pa | ||
| CVE-2026-80694 | Cri | 9.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: net: ethernet: mtk_eth_soc: pass eth to mtk_handle_irq_rx in poll_controller mtk_handle_irq_rx expects a struct mtk_eth * (matching the request_irq cookie), but mtk_poll_controller incorrectly passed the net_de | |
| CVE-2026-80693 | Cri | 9.3 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: idpf: bound interrupt-vector register fill to the allocated array idpf_get_reg_intr_vecs() fills the caller-allocated reg_vals[] array from the VIRTCHNL2_OP_ALLOC_VECTORS reply in adapter->req_vec_chunks, bound | |
| CVE-2026-80692 | Hig | 8.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: hold conn in hci_connect_acl/le_sync() callbacks There is theoretical UAF if the conn is freed while the hci_sync task is running. Hold refcount to avoid that. | |
| CVE-2026-80686 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: mm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE pte_pfn() and pte_dirty() have undefined behaviour when called on a non-present PTE. In migrate_vma_collect_pmd(), these functions may be invo | ||
| CVE-2026-80684 | Cri | 9.3 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: KVM: s390: pci: Fix NULL dereference on AIBV allocation failure The airq_iv_create() can return NULL on failure, but the return value was never checked. If it fails, zdev->aibv will be NULL and fail when derefe | |
| CVE-2026-80683 | Hig | 8.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: give the socket its own sco_conn reference sco_conn_del() drops a reference it does not own. It takes one transient reference via sco_conn_hold_unless_zero() and releases it with the sco_conn_pu | |
| CVE-2026-80681 | Cri | 9.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: vxlan: re-fetch eth header after route_shortcircuit() Before route_shortcircuit(), the eth header pointer is cached from eth_hdr(skb). Inside route_shortcircuit(), pskb_may_pull() can be called, which may real | |
| CVE-2026-80680 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: i2c: amd-mp2: Unregister callback on adapter add failure amd_mp2_register_cb() stores the platform I2C context in the MP2 PCI driver's callback table before the adapter is registered. If i2c_add_adapter() fails | |
| CVE-2026-80679 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Aug 28, 2026 | In the Linux kernel, the following vulnerability has been resolved: s390/dasd: Fix potential NULL pointer dereference dasd_release_space() checks the implementation of the is_ese() discipline function before calling it to determine if a given device is an ESE DASD. The current |
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: s390/zcrypt: Fix wrong domain value verification with EP11 CPRBs There is a wrong upper limit check for the domain value when an EP11 CPRB is processed for sending to a crypto card. This check is only active on
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: can: j1939: transport: j1939_session_fresh_new(): initialize receive buffer Zero the allocated buffer in j1939_session_fresh_new() to ensure it contains no residual data. While there is a potential performance
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: can: softing: fw_parse(): validate firmware record spans fw_parse() reads a fixed record header, a firmware-provided payload, and a trailing checksum without knowing the end of the firmware blob. A truncated re
- CVE-2026-80704Aug 28, 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: use proper context for logging The same as the rest of the code, get_ss_info_from_atombios() uses calc_pll_cs->ctx->logger for logging. But calc_pll_cs->ctx is initialized only later in calc_pl
- CVE-2026-80703Aug 28, 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: Fix missing authorization check in KFD_IOC_DBG_TRAP_DISABLE Prevent unauthorized termination of active GPU debug sessions. Previously, users with /dev/kfd access could terminate another process's de
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: fix guest_memory_dirty bitfield clobbered as size Two sites in vmwgfx_resource.c assign boolean literals to res->guest_memory_size, which is an unsigned long allocation-size field; the intended targ
- CVE-2026-80701Aug 28, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: enforce cursor size limits for MOB cursors vmw_cursor_plane_atomic_check() bounds cursor width and height only on the legacy update path; the SVGA_CAP2_CURSOR_MOB path -- the default on modern hosts
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: validate external BO copy bounds for both stride paths vmw_external_bo_copy() trusts caller-supplied offsets, strides, and heights and operates on imported dma-buf vmaps: - The equal-stride memcp
- CVE-2026-80698Aug 28, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: fix double free of wq, engine, and group structs The release callbacks for wq, engine, and group devices (idxd_conf_wq_release, idxd_conf_engine_release, idxd_conf_group_release) each call kfre
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: hwmon: (ltc4282) Fix reading the minimum alarm voltage Coverity reports an out-of-bounds access when reading the minimum alarm voltage for the VGPIO channel. Add the missing return statement to fix the problem.
- CVE-2026-80695Aug 28, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: hwmon: (sht3x) Fix unaligned accesses Sashiko reports: In sht3x_update_client(), the 16-bit temperature and humidity values are extracted from a stack-allocated byte array using be16_to_cpup(). The pointers pa
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: net: ethernet: mtk_eth_soc: pass eth to mtk_handle_irq_rx in poll_controller mtk_handle_irq_rx expects a struct mtk_eth * (matching the request_irq cookie), but mtk_poll_controller incorrectly passed the net_de
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: idpf: bound interrupt-vector register fill to the allocated array idpf_get_reg_intr_vecs() fills the caller-allocated reg_vals[] array from the VIRTCHNL2_OP_ALLOC_VECTORS reply in adapter->req_vec_chunks, bound
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: hold conn in hci_connect_acl/le_sync() callbacks There is theoretical UAF if the conn is freed while the hci_sync task is running. Hold refcount to avoid that.
- CVE-2026-80686Aug 28, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: mm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE pte_pfn() and pte_dirty() have undefined behaviour when called on a non-present PTE. In migrate_vma_collect_pmd(), these functions may be invo
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: KVM: s390: pci: Fix NULL dereference on AIBV allocation failure The airq_iv_create() can return NULL on failure, but the return value was never checked. If it fails, zdev->aibv will be NULL and fail when derefe
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: SCO: give the socket its own sco_conn reference sco_conn_del() drops a reference it does not own. It takes one transient reference via sco_conn_hold_unless_zero() and releases it with the sco_conn_pu
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: vxlan: re-fetch eth header after route_shortcircuit() Before route_shortcircuit(), the eth header pointer is cached from eth_hdr(skb). Inside route_shortcircuit(), pskb_may_pull() can be called, which may real
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: i2c: amd-mp2: Unregister callback on adapter add failure amd_mp2_register_cb() stores the platform I2C context in the MP2 PCI driver's callback table before the adapter is registered. If i2c_add_adapter() fails
- CVE-2026-80679Aug 28, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: s390/dasd: Fix potential NULL pointer dereference dasd_release_space() checks the implementation of the is_ese() discipline function before calling it to determine if a given device is an ESE DASD. The current
Page 69 of 141