rpm package
opensuse/kernel-obs-qa&distro=openSUSE Leap 16.1
pkg:rpm/opensuse/kernel-obs-qa&distro=openSUSE%20Leap%2016.1
Vulnerabilities (2,819)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-80979 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: net/smc: unregister the connection before draining the rx tasklet smc_conn_free() calls smc_ism_unset_conn() only while the link group is still on its device list, and never sets conn->killed. smc_lgr_terminate | |
| CVE-2026-80978 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: net: cap advertised IP tunnel headroom IP tunnel devices derive their advertised needed_headroom from lower output devices. A stack of user-created devices can make the derived value larger than the 16-bit skb | |
| CVE-2026-80977 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: net: skbuff: don't touch shared zerocopy state in skb_tx_error() skb_tx_error() completes the zerocopy uarg and clears SKBFL_ALL_ZEROCOPY, and skb_zcopy_downgrade_managed() clears SKBFL_MANAGED_FRAG_REFS. Both | |
| CVE-2026-80976 | Cri | 9.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: seg6: reset IP6CB after IPv6 decapsulation decap_and_validate() pulls the outer SRv6 headers and makes the inner packet the skb network header. The IPv6 control block still contains values collected while parsi | |
| CVE-2026-80974 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: mfd: sm501: Fix potential memory leaks during remove The memory allocated for struct sm501_devdata in sm501_pci_probe() and sm501_plat_probe() is not freed by the corresponding remove functions sm501_pci_remove | ||
| CVE-2026-80973 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: ALSA: 6fire: bound the MIDI event length from the device usb6fire_comm_receiver_handler() forwards a MIDI event using a length byte the device supplies, with no bound and no check that the transfer delivered th | ||
| CVE-2026-80972 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: ALSA: aloop: Check card index validity at probe aloop driver blindly trusts that the given devptr->id value is within the proper card index range at probe. It's OK for the devices the driver itself creates at | ||
| CVE-2026-80971 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: ALSA: bcd2000: clear the URB pointers on disconnect bcd2000_free_usb_related_resources() frees both URBs and leaves the pointers behind: usb_kill_urb(bcd2k->midi_out_urb); usb_kill_urb(bcd2k->midi_in_urb); | |
| CVE-2026-80970 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: ALSA: FCP: do not copy out an uninitialised init response fcp_ioctl_init() allocates its response buffer with kmalloc() and copies the whole buffer back to userspace: buf_size = init.step0_resp_size + init.st | ||
| CVE-2026-80969 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: ALSA: mpu401: Check card index validity at probe mpu401 driver blindly trusts that the given devptr->id value is within the proper card index range at probe. It's OK for the devices the driver itself creates a | ||
| CVE-2026-80968 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: ALSA: mts64: Check card index validity at probe Although mts64 driver has a check of the given devptr->id value, it doesn't check for a negative id, which is often given as "none" or such value when bound via s | ||
| CVE-2026-80967 | Hig | 8.4 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: ALSA: pcxhr: initialize mutexes before requesting threaded IRQ pcxhr_probe() requests pcxhr_threaded_irq() before initializing mgr->lock, even though the threaded handler takes that mutex. Initialize the manag | |
| CVE-2026-80966 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: ALSA: portman2x4: Check card index validity at probe Although portman2x4 driver has a check of the given devptr->id value, it doesn't check for a negative id, which is often given as "none" or such value when b | ||
| CVE-2026-80965 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: ALSA: serial-u16550: Check card index validity at probe serial-u16550 driver blindly trusts that the given devptr->id value is within the proper card index range at probe. It's OK for the devices the driver it | ||
| CVE-2026-80964 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: ALSA: virmidi: Check card index validity at probe virmidi driver blindly trusts that the given devptr->id value is within the proper card index range at probe. It's OK for the devices the driver itself creates | ||
| CVE-2026-80952 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: i3c: master: Fix info leak and UAF in device unregister path i3c_master_unregister_i3c_devs() clears i3cdev->dev->desc before calling device_unregister(). During device_unregister(), device_del() emits a KOBJ_ | |
| CVE-2026-80951 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: i3c: master: svc: bound IBI payload to the requested max_payload_len svc_i3c_master_handle_ibi() reads the IBI payload from the RX FIFO into the IBI slot. The loop is bounded by the hardware FIFO size (SVC_I3C_ | ||
| CVE-2026-80949 | — | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: Fix memory leak in brcmf_sdio_read_control() The memory allocated for buf is not freed in some of the error paths in brcmf_sdio_read_control(). Fix that by adding vfree() calls. [arend: rework | ||
| CVE-2026-80947 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop rtl8xxxu arms rx_urb_wq from the RX completion path: rtl8xxxu_rx_complete() hands the URB to rtl8xxxu_queue_rx_urb(), which queues it on rx_urb_pending_ | |
| CVE-2026-80944 | Hig | 7.8 | < 6.12.0-160100.9.1 | 6.12.0-160100.9.1 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Detach sync cmd buffer on interrupted wait mwifiex synchronous commands keep the caller-provided data buffer in cmd_node->data_buf. Several callers pass stack-allocated objects there. If wait_ev |
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: net/smc: unregister the connection before draining the rx tasklet smc_conn_free() calls smc_ism_unset_conn() only while the link group is still on its device list, and never sets conn->killed. smc_lgr_terminate
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: net: cap advertised IP tunnel headroom IP tunnel devices derive their advertised needed_headroom from lower output devices. A stack of user-created devices can make the derived value larger than the 16-bit skb
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: net: skbuff: don't touch shared zerocopy state in skb_tx_error() skb_tx_error() completes the zerocopy uarg and clears SKBFL_ALL_ZEROCOPY, and skb_zcopy_downgrade_managed() clears SKBFL_MANAGED_FRAG_REFS. Both
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: seg6: reset IP6CB after IPv6 decapsulation decap_and_validate() pulls the outer SRv6 headers and makes the inner packet the skb network header. The IPv6 control block still contains values collected while parsi
- CVE-2026-80974Sep 11, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: mfd: sm501: Fix potential memory leaks during remove The memory allocated for struct sm501_devdata in sm501_pci_probe() and sm501_plat_probe() is not freed by the corresponding remove functions sm501_pci_remove
- CVE-2026-80973Sep 11, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: ALSA: 6fire: bound the MIDI event length from the device usb6fire_comm_receiver_handler() forwards a MIDI event using a length byte the device supplies, with no bound and no check that the transfer delivered th
- CVE-2026-80972Sep 11, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: ALSA: aloop: Check card index validity at probe aloop driver blindly trusts that the given devptr->id value is within the proper card index range at probe. It's OK for the devices the driver itself creates at
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: ALSA: bcd2000: clear the URB pointers on disconnect bcd2000_free_usb_related_resources() frees both URBs and leaves the pointers behind: usb_kill_urb(bcd2k->midi_out_urb); usb_kill_urb(bcd2k->midi_in_urb);
- CVE-2026-80970Sep 11, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: ALSA: FCP: do not copy out an uninitialised init response fcp_ioctl_init() allocates its response buffer with kmalloc() and copies the whole buffer back to userspace: buf_size = init.step0_resp_size + init.st
- CVE-2026-80969Sep 11, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: ALSA: mpu401: Check card index validity at probe mpu401 driver blindly trusts that the given devptr->id value is within the proper card index range at probe. It's OK for the devices the driver itself creates a
- CVE-2026-80968Sep 11, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: ALSA: mts64: Check card index validity at probe Although mts64 driver has a check of the given devptr->id value, it doesn't check for a negative id, which is often given as "none" or such value when bound via s
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: ALSA: pcxhr: initialize mutexes before requesting threaded IRQ pcxhr_probe() requests pcxhr_threaded_irq() before initializing mgr->lock, even though the threaded handler takes that mutex. Initialize the manag
- CVE-2026-80966Sep 11, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: ALSA: portman2x4: Check card index validity at probe Although portman2x4 driver has a check of the given devptr->id value, it doesn't check for a negative id, which is often given as "none" or such value when b
- CVE-2026-80965Sep 11, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: ALSA: serial-u16550: Check card index validity at probe serial-u16550 driver blindly trusts that the given devptr->id value is within the proper card index range at probe. It's OK for the devices the driver it
- CVE-2026-80964Sep 11, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: ALSA: virmidi: Check card index validity at probe virmidi driver blindly trusts that the given devptr->id value is within the proper card index range at probe. It's OK for the devices the driver itself creates
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: i3c: master: Fix info leak and UAF in device unregister path i3c_master_unregister_i3c_devs() clears i3cdev->dev->desc before calling device_unregister(). During device_unregister(), device_del() emits a KOBJ_
- CVE-2026-80951Sep 11, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: i3c: master: svc: bound IBI payload to the requested max_payload_len svc_i3c_master_handle_ibi() reads the IBI payload from the RX FIFO into the IBI slot. The loop is bounded by the hardware FIFO size (SVC_I3C_
- CVE-2026-80949Sep 11, 2026affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: Fix memory leak in brcmf_sdio_read_control() The memory allocated for buf is not freed in some of the error paths in brcmf_sdio_read_control(). Fix that by adding vfree() calls. [arend: rework
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop rtl8xxxu arms rx_urb_wq from the RX completion path: rtl8xxxu_rx_complete() hands the URB to rtl8xxxu_queue_rx_urb(), which queues it on rx_urb_pending_
- affected < 6.12.0-160100.9.1fixed 6.12.0-160100.9.1
In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Detach sync cmd buffer on interrupted wait mwifiex synchronous commands keep the caller-provided data buffer in cmd_node->data_buf. Several callers pass stack-allocated objects there. If wait_ev
Page 62 of 141