rpm package
opensuse/kernel-source&distro=openSUSE Tumbleweed
pkg:rpm/opensuse/kernel-source&distro=openSUSE%20Tumbleweed
Vulnerabilities (4,006)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-97920 | — | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: tracing: Keep the entry count when the histogram stats allocation fails print_entries() uses n_entries both as the number of sort entries and as its own return value, so the -ENOMEM it stores when the stats all | ||
| CVE-2026-97919 | — | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: tracing: Take the reference before publishing the named histogram trigger event_hist_trigger_named_init() puts the trigger on the global named_triggers list and only then takes the reference on the trigger it s | ||
| CVE-2026-97918 | — | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: tracing: Undo the registration when enabling the histogram trigger fails Commit 6f86bdeab633 ("tracing: Fix bad hist from corrupting named_triggers list") described how a trigger that is registered but not on f | ||
| CVE-2026-97917 | — | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Validate full buffer range in ivpu_to_cpu_addr Add a size parameter to ivpu_to_cpu_addr() and validate that the whole [vpu_addr, vpu_addr + size) range stays within the BO. | ||
| CVE-2026-97916 | — | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Validate firmware log buffer metadata The tracing log headers parsed by fw_log_print_buffer() reside in DMA-shared BOs that the NPU firmware can write to. fw_log_from_bo() validated log->header_siz | ||
| CVE-2026-97915 | — | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Limit firmware log name prints to field size The name in struct vpu_tracing_buffer_header is a fixed-size array populated by the NPU firmware. It is expected to be NUL-terminated, but nothing on the | ||
| CVE-2026-97914 | — | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: accel: ethosu: Fix ethosu_job_open() return value A WARN_ON() returns a 0 or 1, not the original negative errno. Just drop the WARN_ON() as the FD open will pass the return code to userspace and there's only on | ||
| CVE-2026-97913 | — | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: accel: ethosu: Ensure cmd stream ends with a stop op While the QSIZE register setting should prevent an out of bounds access of the command stream, it is not clear whether the h/w generates an interrupt in this | ||
| CVE-2026-97912 | — | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: accel: ethosu: Ensure SRAM size is 0 on mapping failure On a mapping failure of the SRAM, the SRAM size is left as non-zero. The probe will succeed as the error return is not checked since having SRAM is not a | ||
| CVE-2026-97911 | Hig | 7.8 | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: accel: ethosu: Ensure SRAM region size matches job It is possible for userspace to set the job SRAM size to 0, but then still have SRAM accesses in the command stream. When the job SRAM size is 0, setting the r | |
| CVE-2026-97910 | Hig | 7.8 | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: ASoC: sprd: validate compress buffer sizes against fixed allocations sprd_platform_compr_open() allocates the stage 0 IRAM buffer (32K data area) and the stage 1 DDR buffer (2M data area) with fixed sizes, but | |
| CVE-2026-97909 | — | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: ASoC: sti: initialize IRQ lock before requesting IRQ uni_reader_init() registers the shared IRQ before initializing reader->irq_lock. A pending interrupt can invoke the handler while the lock is still uninitial | ||
| CVE-2026-97908 | — | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev The command and ACL RPMsg endpoints store struct btqcomsmd as their callback private data. The receive callbacks dereference btq->hdev withou | ||
| CVE-2026-97907 | — | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btrtl: Don't leak return code when parsing firmware format v2 When key_id from chip is zero, rtlbt_parse_firmware_v2() intentionally ignores all security headers. However, the implementation simply b | ||
| CVE-2026-97906 | — | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: bootconfig: Fix integer overflow in initrd size check Sashiko reported that in get_boot_config_from_initrd(), a crafted initrd with a huge bootconfig size (such as 0xFFFFFFFF) can cause the pointer arithmetic: | ||
| CVE-2026-97905 | — | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: cpufreq: zero-initialize policy cpumask before sysfs publication cpufreq_policy_alloc() allocates policy->cpus with alloc_cpumask_var(), i.e. without __GFP_ZERO, unlike the sibling related_cpus and real_cpus ma | ||
| CVE-2026-97904 | — | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: cpufreq: initialize policy rwsem before sysfs publication cpufreq_policy_alloc() initializes policy->rwsem after kobject_init_and_add() has created the policy sysfs directory and its default attributes. A sysfs | ||
| CVE-2026-97903 | Hig | 7.8 | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: exit: hold a reference to thread_pid across proc_flush_pid Commit 0a36bad01731 ("release_task: kill the no longer needed get/put_pid(thread_pid)") removed the reference around proc_flush_pid(). It assumed that | |
| CVE-2026-97902 | — | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: fs: don't return -EINVAL for successful nested thaw Commit 7366f8b6fc6a ("fs: handle freezing from multiple devices") replaced the freeze_holders bitmask with per-holder counters to allow nested freezes. In the | ||
| CVE-2026-97901 | — | < 7.2.9-1.1 | 7.2.9-1.1 | Sep 25, 2026 | In the Linux kernel, the following vulnerability has been resolved: genetlink: pin family module during policy dump The generic netlink controller's policy dump keeps pointers to the target family's operation and policy tables in its callback state. A dump may be split across |
- CVE-2026-97920Sep 25, 2026affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: tracing: Keep the entry count when the histogram stats allocation fails print_entries() uses n_entries both as the number of sort entries and as its own return value, so the -ENOMEM it stores when the stats all
- CVE-2026-97919Sep 25, 2026affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: tracing: Take the reference before publishing the named histogram trigger event_hist_trigger_named_init() puts the trigger on the global named_triggers list and only then takes the reference on the trigger it s
- CVE-2026-97918Sep 25, 2026affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: tracing: Undo the registration when enabling the histogram trigger fails Commit 6f86bdeab633 ("tracing: Fix bad hist from corrupting named_triggers list") described how a trigger that is registered but not on f
- CVE-2026-97917Sep 25, 2026affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Validate full buffer range in ivpu_to_cpu_addr Add a size parameter to ivpu_to_cpu_addr() and validate that the whole [vpu_addr, vpu_addr + size) range stays within the BO.
- CVE-2026-97916Sep 25, 2026affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Validate firmware log buffer metadata The tracing log headers parsed by fw_log_print_buffer() reside in DMA-shared BOs that the NPU firmware can write to. fw_log_from_bo() validated log->header_siz
- CVE-2026-97915Sep 25, 2026affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: accel/ivpu: Limit firmware log name prints to field size The name in struct vpu_tracing_buffer_header is a fixed-size array populated by the NPU firmware. It is expected to be NUL-terminated, but nothing on the
- CVE-2026-97914Sep 25, 2026affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: accel: ethosu: Fix ethosu_job_open() return value A WARN_ON() returns a 0 or 1, not the original negative errno. Just drop the WARN_ON() as the FD open will pass the return code to userspace and there's only on
- CVE-2026-97913Sep 25, 2026affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: accel: ethosu: Ensure cmd stream ends with a stop op While the QSIZE register setting should prevent an out of bounds access of the command stream, it is not clear whether the h/w generates an interrupt in this
- CVE-2026-97912Sep 25, 2026affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: accel: ethosu: Ensure SRAM size is 0 on mapping failure On a mapping failure of the SRAM, the SRAM size is left as non-zero. The probe will succeed as the error return is not checked since having SRAM is not a
- affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: accel: ethosu: Ensure SRAM region size matches job It is possible for userspace to set the job SRAM size to 0, but then still have SRAM accesses in the command stream. When the job SRAM size is 0, setting the r
- affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: ASoC: sprd: validate compress buffer sizes against fixed allocations sprd_platform_compr_open() allocates the stage 0 IRAM buffer (32K data area) and the stage 1 DDR buffer (2M data area) with fixed sizes, but
- CVE-2026-97909Sep 25, 2026affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: ASoC: sti: initialize IRQ lock before requesting IRQ uni_reader_init() registers the shared IRQ before initializing reader->irq_lock. A pending interrupt can invoke the handler while the lock is still uninitial
- CVE-2026-97908Sep 25, 2026affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev The command and ACL RPMsg endpoints store struct btqcomsmd as their callback private data. The receive callbacks dereference btq->hdev withou
- CVE-2026-97907Sep 25, 2026affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btrtl: Don't leak return code when parsing firmware format v2 When key_id from chip is zero, rtlbt_parse_firmware_v2() intentionally ignores all security headers. However, the implementation simply b
- CVE-2026-97906Sep 25, 2026affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: bootconfig: Fix integer overflow in initrd size check Sashiko reported that in get_boot_config_from_initrd(), a crafted initrd with a huge bootconfig size (such as 0xFFFFFFFF) can cause the pointer arithmetic:
- CVE-2026-97905Sep 25, 2026affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: cpufreq: zero-initialize policy cpumask before sysfs publication cpufreq_policy_alloc() allocates policy->cpus with alloc_cpumask_var(), i.e. without __GFP_ZERO, unlike the sibling related_cpus and real_cpus ma
- CVE-2026-97904Sep 25, 2026affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: cpufreq: initialize policy rwsem before sysfs publication cpufreq_policy_alloc() initializes policy->rwsem after kobject_init_and_add() has created the policy sysfs directory and its default attributes. A sysfs
- affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: exit: hold a reference to thread_pid across proc_flush_pid Commit 0a36bad01731 ("release_task: kill the no longer needed get/put_pid(thread_pid)") removed the reference around proc_flush_pid(). It assumed that
- CVE-2026-97902Sep 25, 2026affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: fs: don't return -EINVAL for successful nested thaw Commit 7366f8b6fc6a ("fs: handle freezing from multiple devices") replaced the freeze_holders bitmask with per-holder counters to allow nested freezes. In the
- CVE-2026-97901Sep 25, 2026affected < 7.2.9-1.1fixed 7.2.9-1.1
In the Linux kernel, the following vulnerability has been resolved: genetlink: pin family module during policy dump The generic netlink controller's policy dump keeps pointers to the target family's operation and policy tables in its callback state. A dump may be split across
Page 27 of 201