rpm package
opensuse/kernel-syms&distro=openSUSE Leap 16.1
pkg:rpm/opensuse/kernel-syms&distro=openSUSE%20Leap%2016.1
Vulnerabilities (2,819)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-93056 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_uac1_legacy: remove broken string configfs attributes The UAC1_STR_ATTRIBUTE macro defines configfs show/store handlers for the fn_play, fn_cap, and fn_cntl string options. The store function con | ||
| CVE-2026-93054 | Hig | 7.0 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: uio: Fix stale info pointer in failed registration path After device_add(), the UIO device is visible to userspace and /dev/uioX can be opened. If a later setup step fails, __uio_register_device() unwinds the d | |
| CVE-2026-93053 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: speakup: keyhelp: guard letter_offsets possible out-of-range indexing help_init() builds letter_offsets[] by using the first byte of each function name as an index via `(start & 31) - 1`. If function_names are | ||
| CVE-2026-93052 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: misc: bcm-vk: Use acquire/release for msgq_inited bcm_vk_sync_msgq() fills the message queue information and then sets msgq_inited. Readers call bcm_vk_drv_access_ok() before accessing the message queues and th | ||
| CVE-2026-93049 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: mtd: mtdswap: Avoid freeing registered blktrans device twice In mtdswap_add_mtd(), debugfs setup failure after successful blktrans registration can free mbd_dev twice. add_mtd_blktrans_dev() initializes the bl | ||
| CVE-2026-93048 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: mtd: part: reject MTDPART_OFS_RETAIN in mtd_add_partition() mtd_add_partition() does not reject the special offset value MTDPART_OFS_RETAIN (-3), which leads to a WARN_ON in add_mtd_device() when called through | ||
| CVE-2026-93046 | Hig | 7.0 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: software node: Fix software_node_get_reference_args() with index -1 The bounds check for the index passed to software_node_get_reference_args() was failing when passed UINT_MAX, this in turn would lead to an ou | |
| CVE-2026-93042 | Hig | 8.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: dmaengine: dw-edma: Terminate all descriptors without callbacks The DMA Engine client documentation says in the "Terminate APIs" section of Documentation/driver-api/dmaengine/client.rst: "No callback functions | |
| CVE-2026-93041 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: dmaengine: dw-edma: Serialize abort state updates dw_edma_abort_interrupt() drops vc.lock before changing request and status. issue_pending() can acquire the lock in that small window, observe the old busy stat | ||
| CVE-2026-93040 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: dmaengine: dw-edma: Serialize channel state checks pause() and resume() read and update channel state without holding vc.lock, while the interrupt handlers update the same state under it. Take the same lock aro | ||
| CVE-2026-93037 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Propagate sdma_txinit_ahg() errors set_txreq_header_ahg() ignores the return value of sdma_txinit_ahg(). If sdma_txinit_ahg() fails, it returns before initializing tx->txreq. However, set_txreq_head | |
| CVE-2026-92525 | Hig | 7.1 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Validate num_sge/cur_sge before indexing wqe->dma.sge[] For a user QP, qp->sq.queue is a ring the application writes directly, so rxe_post_send() takes the is_user branch and only schedules send_task | |
| CVE-2026-92523 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: RDMA/nldev: validate dynamic counter attribute length RDMA_NLDEV_ATTR_STAT_HWCOUNTERS is a nested attribute whose children are consumed directly with nla_get_u32(). The top-level policy validates only the conta | ||
| CVE-2026-92522 | Hig | 7.3 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: ACPI: processor: validate MADT IOAPIC entry bounds The IOAPIC hotplug lookup parses both MADT and _MAT records directly. The MADT walk previously used a subtable's declared length to advance the cursor after on | |
| CVE-2026-92521 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: ACPI: PCI: Clear driver_data on all paths that free the acpi_pci_root acpi_pci_root_add() assigns the freshly allocated root to device->driver_data before dmar_device_add() and pci_acpi_scan_root(). Both failur | ||
| CVE-2026-92513 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: RDMA/mana_ib: drain QP references after partial table insertion mana_table_store_ud_qp() publishes a QP at its send-queue id before inserting the receive-queue id, dropping the XArray lock between the two xa_in | ||
| CVE-2026-92512 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix use after free in ib_query_qp() When querying a QP via the netlink flow the only synchronization mechanism for the said QP is rdma_restrack_get(), meanwhile during the QP destroy path rdma_restra | ||
| CVE-2026-92511 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix potential use after free in ib_destroy_cq_user() When accessing a CQ via the netlink path the only synchronization mechanism for the said CQ is rdma_restrack_get(). Currently, rdma_restrack_del() | |
| CVE-2026-92510 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix potential use after free in ib_destroy_srq_user() When accessing a SRQ via the netlink path the only synchronization mechanism for the said SRQ is rdma_restrack_get(). Currently, rdma_restrack_de | |
| CVE-2026-92509 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 17, 2026 | In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix potential use after free in counter_release() When accessing a counter via the netlink path the only synchronization mechanism for the said counter is rdma_restrack_get(). Currently, rdma_restrac |
- CVE-2026-93056Sep 17, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_uac1_legacy: remove broken string configfs attributes The UAC1_STR_ATTRIBUTE macro defines configfs show/store handlers for the fn_play, fn_cap, and fn_cntl string options. The store function con
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: uio: Fix stale info pointer in failed registration path After device_add(), the UIO device is visible to userspace and /dev/uioX can be opened. If a later setup step fails, __uio_register_device() unwinds the d
- CVE-2026-93053Sep 17, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: speakup: keyhelp: guard letter_offsets possible out-of-range indexing help_init() builds letter_offsets[] by using the first byte of each function name as an index via `(start & 31) - 1`. If function_names are
- CVE-2026-93052Sep 17, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: misc: bcm-vk: Use acquire/release for msgq_inited bcm_vk_sync_msgq() fills the message queue information and then sets msgq_inited. Readers call bcm_vk_drv_access_ok() before accessing the message queues and th
- CVE-2026-93049Sep 17, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: mtd: mtdswap: Avoid freeing registered blktrans device twice In mtdswap_add_mtd(), debugfs setup failure after successful blktrans registration can free mbd_dev twice. add_mtd_blktrans_dev() initializes the bl
- CVE-2026-93048Sep 17, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: mtd: part: reject MTDPART_OFS_RETAIN in mtd_add_partition() mtd_add_partition() does not reject the special offset value MTDPART_OFS_RETAIN (-3), which leads to a WARN_ON in add_mtd_device() when called through
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: software node: Fix software_node_get_reference_args() with index -1 The bounds check for the index passed to software_node_get_reference_args() was failing when passed UINT_MAX, this in turn would lead to an ou
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: dmaengine: dw-edma: Terminate all descriptors without callbacks The DMA Engine client documentation says in the "Terminate APIs" section of Documentation/driver-api/dmaengine/client.rst: "No callback functions
- CVE-2026-93041Sep 17, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: dmaengine: dw-edma: Serialize abort state updates dw_edma_abort_interrupt() drops vc.lock before changing request and status. issue_pending() can acquire the lock in that small window, observe the old busy stat
- CVE-2026-93040Sep 17, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: dmaengine: dw-edma: Serialize channel state checks pause() and resume() read and update channel state without holding vc.lock, while the interrupt handlers update the same state under it. Take the same lock aro
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Propagate sdma_txinit_ahg() errors set_txreq_header_ahg() ignores the return value of sdma_txinit_ahg(). If sdma_txinit_ahg() fails, it returns before initializing tx->txreq. However, set_txreq_head
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Validate num_sge/cur_sge before indexing wqe->dma.sge[] For a user QP, qp->sq.queue is a ring the application writes directly, so rxe_post_send() takes the is_user branch and only schedules send_task
- CVE-2026-92523Sep 17, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: RDMA/nldev: validate dynamic counter attribute length RDMA_NLDEV_ATTR_STAT_HWCOUNTERS is a nested attribute whose children are consumed directly with nla_get_u32(). The top-level policy validates only the conta
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: ACPI: processor: validate MADT IOAPIC entry bounds The IOAPIC hotplug lookup parses both MADT and _MAT records directly. The MADT walk previously used a subtable's declared length to advance the cursor after on
- CVE-2026-92521Sep 17, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: ACPI: PCI: Clear driver_data on all paths that free the acpi_pci_root acpi_pci_root_add() assigns the freshly allocated root to device->driver_data before dmar_device_add() and pci_acpi_scan_root(). Both failur
- CVE-2026-92513Sep 17, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: RDMA/mana_ib: drain QP references after partial table insertion mana_table_store_ud_qp() publishes a QP at its send-queue id before inserting the receive-queue id, dropping the XArray lock between the two xa_in
- CVE-2026-92512Sep 17, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix use after free in ib_query_qp() When querying a QP via the netlink flow the only synchronization mechanism for the said QP is rdma_restrack_get(), meanwhile during the QP destroy path rdma_restra
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix potential use after free in ib_destroy_cq_user() When accessing a CQ via the netlink path the only synchronization mechanism for the said CQ is rdma_restrack_get(). Currently, rdma_restrack_del()
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix potential use after free in ib_destroy_srq_user() When accessing a SRQ via the netlink path the only synchronization mechanism for the said SRQ is rdma_restrack_get(). Currently, rdma_restrack_de
- CVE-2026-92509Sep 17, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix potential use after free in counter_release() When accessing a counter via the netlink path the only synchronization mechanism for the said counter is rdma_restrack_get(). Currently, rdma_restrac
Page 37 of 141