rpm package
opensuse/kernel-default-base&distro=openSUSE Leap 16.1
pkg:rpm/opensuse/kernel-default-base&distro=openSUSE%20Leap%2016.1
Vulnerabilities (2,819)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-89503 | Hig | 7.8 | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix subbuf resize race with ring_buffer_alloc_read_page() ring_buffer_alloc_read_page() is racy with ring_buffer_subbuf_order_set, it can allocate a reader page with an outdated order. This isn't a | |
| CVE-2026-89502 | — | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Free cpu_buffer::free_page with subbuf_order When sub-buffers use an order greater than 0, cpu_buffer->free_page is allocated with subbuf_order. Use the correct order for cpu_buffer->free_page. | ||
| CVE-2026-89501 | Hig | 7.8 | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Hold cpu_buffer::lock when resizing a subbuf Because, ring_buffer_subbuf_order_set() can clear cpu_buffer->free_page, hold cpu_buffer->lock to prevent races with ring_buffer_alloc_read_page() and r | |
| CVE-2026-89500 | Hig | 7.8 | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Make cpu_buffer::free_page a buffer_data_read_page Discarding a cached reader page after a concurrent ring buffer resize uses the new global subbuf_order for the free_pages() call. This mismatched | |
| CVE-2026-89495 | Cri | 9.8 | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: ocfs2: bound namelen in dlm_migrate_request_handler Patch series "ocfs2/dlm: bound peer-controlled lengths in the o2dlm". The o2dlm receive handlers trust u8 length and count fields from the wire without bound | |
| CVE-2026-89494 | Cri | 9.8 | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: ocfs2: validate lengths in dlm_mig_lockres_handler A node receiving a DLM_MIG_LOCKRES message trusts several fields of the peer-supplied dlm_migratable_lockres without validation. num_locks and lockname_len ar | |
| CVE-2026-89491 | — | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: ocfs2: cluster: don't sleep while holding o2hb_live_lock in o2hb_region_pin() Patch series "ocfs2: cluster: o2hb_region_pin() fixes", v2. This series fixes three related issues in o2hb_region_pin(), all are fr | ||
| CVE-2026-89485 | Cri | 9.8 | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: lockd: pin next file across nlm_inspect_file lock-drop nlm_traverse_files() pins the current file with f_count++ across a mutex_unlock for nlm_inspect_file(), but nothing pins the saved next pointer. A concurr | |
| CVE-2026-89482 | Cri | 9.8 | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone Commit 25e5cb780e62 ("nvme-tcp: fix possible crash in write_zeroes processing") established that blk_rq_payload_bytes() must not be read wit | |
| CVE-2026-89481 | Hig | 7.5 | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: fix host memory disclosure on R2T for a read command nvme_tcp_handle_r2t() does not check the direction of the request the R2T refers to. A malicious controller can send an R2T for a READ and the host | |
| CVE-2026-89480 | Hig | 7.5 | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: reject a read that transferred too few bytes nvme_tcp_recv_data() completes a request once the current C2HData PDU has been consumed. Nothing compares the total bytes received against the length the c | |
| CVE-2026-89479 | Cri | 9.8 | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: sctp: stop processing a packet once its association is deleted sctp_endpoint_bh_rcv() looks the association up only when chunk->asoc is NULL, and caches the result in chunk->asoc and chunk->transport without ta | |
| CVE-2026-89477 | Hig | 7.5 | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: sctp: fix NULL deref on untransmitted RECONF completion sctp_process_strreset_outreq(), sctp_process_strreset_addstrm_out() and sctp_process_strreset_resp() complete a pending stream reconfiguration request by | |
| CVE-2026-89475 | — | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: power: supply: bq24257: fix use-after-free on remove The STAT-pin interrupt is devm-managed, so it stays armed until the devm cleanup that runs after remove() returns. remove() cancels bq->iilimit_setup_work wh | ||
| CVE-2026-89474 | — | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: power: supply: bq256xx: drain usb_work before freeing the charger The USB-PHY notifier queues usb_work, whose handler calls power_supply_changed(bq->charger). The reset devm action only unregisters the notifier | ||
| CVE-2026-89473 | — | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: power: supply: bq25890: Fix power_supply reference leak bq25890_fw_probe() acquires a reference to a secondary charger using power_supply_get_by_name(), but the reference is not released on later probe failures | ||
| CVE-2026-89472 | Hig | 7.8 | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: power: supply: charger-manager: register regulators before exposing sysfs charger_manager_remove() and the err_reg_extcon probe error path free each charger regulator with regulator_put() before tearing down th | |
| CVE-2026-89471 | Hig | 8.4 | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: power: supply: cros_usbpd-charger: bound the EC-reported port count cros_usbpd_charger_probe() reads two port counts from the EC and uses one of them, num_charger_ports, as the loop bound when populating a fixe | |
| CVE-2026-89470 | Hig | 8.4 | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: power: supply: cros_usbpd: Limit port counts to EC_USB_PD_MAX_PORTS Currently the cros_usbpd-charger driver probe iterates based on raw charger port count returned by the embedded controller. The only check is | |
| CVE-2026-89469 | Hig | 8.4 | < 6.12.0-160100.9.1.160100.3.14 | 6.12.0-160100.9.1.160100.3.14 | Sep 11, 2026 | In the Linux kernel, the following vulnerability has been resolved: power: supply: lp8727: fix use-after-free in lp8727_release_irq() lp8727_isr_func(), the threaded IRQ handler, is the only caller that arms pchg->work via schedule_delayed_work(). lp8727_release_irq() currentl |
- affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix subbuf resize race with ring_buffer_alloc_read_page() ring_buffer_alloc_read_page() is racy with ring_buffer_subbuf_order_set, it can allocate a reader page with an outdated order. This isn't a
- CVE-2026-89502Sep 11, 2026affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Free cpu_buffer::free_page with subbuf_order When sub-buffers use an order greater than 0, cpu_buffer->free_page is allocated with subbuf_order. Use the correct order for cpu_buffer->free_page.
- affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Hold cpu_buffer::lock when resizing a subbuf Because, ring_buffer_subbuf_order_set() can clear cpu_buffer->free_page, hold cpu_buffer->lock to prevent races with ring_buffer_alloc_read_page() and r
- affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Make cpu_buffer::free_page a buffer_data_read_page Discarding a cached reader page after a concurrent ring buffer resize uses the new global subbuf_order for the free_pages() call. This mismatched
- affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: ocfs2: bound namelen in dlm_migrate_request_handler Patch series "ocfs2/dlm: bound peer-controlled lengths in the o2dlm". The o2dlm receive handlers trust u8 length and count fields from the wire without bound
- affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: ocfs2: validate lengths in dlm_mig_lockres_handler A node receiving a DLM_MIG_LOCKRES message trusts several fields of the peer-supplied dlm_migratable_lockres without validation. num_locks and lockname_len ar
- CVE-2026-89491Sep 11, 2026affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: ocfs2: cluster: don't sleep while holding o2hb_live_lock in o2hb_region_pin() Patch series "ocfs2: cluster: o2hb_region_pin() fixes", v2. This series fixes three related issues in o2hb_region_pin(), all are fr
- affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: lockd: pin next file across nlm_inspect_file lock-drop nlm_traverse_files() pins the current file with f_count++ across a mutex_unlock for nlm_inspect_file(), but nothing pins the saved next pointer. A concurr
- affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: do not accept C2HData based on blk_rq_payload_bytes() alone Commit 25e5cb780e62 ("nvme-tcp: fix possible crash in write_zeroes processing") established that blk_rq_payload_bytes() must not be read wit
- affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: fix host memory disclosure on R2T for a read command nvme_tcp_handle_r2t() does not check the direction of the request the R2T refers to. A malicious controller can send an R2T for a READ and the host
- affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: reject a read that transferred too few bytes nvme_tcp_recv_data() completes a request once the current C2HData PDU has been consumed. Nothing compares the total bytes received against the length the c
- affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: sctp: stop processing a packet once its association is deleted sctp_endpoint_bh_rcv() looks the association up only when chunk->asoc is NULL, and caches the result in chunk->asoc and chunk->transport without ta
- affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: sctp: fix NULL deref on untransmitted RECONF completion sctp_process_strreset_outreq(), sctp_process_strreset_addstrm_out() and sctp_process_strreset_resp() complete a pending stream reconfiguration request by
- CVE-2026-89475Sep 11, 2026affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: power: supply: bq24257: fix use-after-free on remove The STAT-pin interrupt is devm-managed, so it stays armed until the devm cleanup that runs after remove() returns. remove() cancels bq->iilimit_setup_work wh
- CVE-2026-89474Sep 11, 2026affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: power: supply: bq256xx: drain usb_work before freeing the charger The USB-PHY notifier queues usb_work, whose handler calls power_supply_changed(bq->charger). The reset devm action only unregisters the notifier
- CVE-2026-89473Sep 11, 2026affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: power: supply: bq25890: Fix power_supply reference leak bq25890_fw_probe() acquires a reference to a secondary charger using power_supply_get_by_name(), but the reference is not released on later probe failures
- affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: power: supply: charger-manager: register regulators before exposing sysfs charger_manager_remove() and the err_reg_extcon probe error path free each charger regulator with regulator_put() before tearing down th
- affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: power: supply: cros_usbpd-charger: bound the EC-reported port count cros_usbpd_charger_probe() reads two port counts from the EC and uses one of them, num_charger_ports, as the loop bound when populating a fixe
- affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: power: supply: cros_usbpd: Limit port counts to EC_USB_PD_MAX_PORTS Currently the cros_usbpd-charger driver probe iterates based on raw charger port count returned by the embedded controller. The only check is
- affected < 6.12.0-160100.9.1.160100.3.14fixed 6.12.0-160100.9.1.160100.3.14
In the Linux kernel, the following vulnerability has been resolved: power: supply: lp8727: fix use-after-free in lp8727_release_irq() lp8727_isr_func(), the threaded IRQ handler, is the only caller that arms pchg->work via schedule_delayed_work(). lp8727_release_irq() currentl
Page 59 of 141