https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 09:48:58 +0000 https://cve.radiocsirt.org/vuln/bdu:2024-03616 bdu:2024-03616 https://cve.radiocsirt.org/vuln/bdu:2024-03616 https://cve.radiocsirt.org/vuln/bell-cve-2024-26646 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2024-26646 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0329 certfr-2024-avi-0329 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0329 https://cve.radiocsirt.org/vuln/euvd-2026-345478 EUVD-2026-345478 https://cve.radiocsirt.org/vuln/euvd-2026-345478 https://cve.radiocsirt.org/vuln/fkie_cve-2024-26646 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>thermal: intel: hfi: Add syscore callbacks for system-wide PM</p> <p>The kernel allocates a memory buffer and provides its location to the hardware, which uses it to update the HFI table. This allocation occurs during boot and remains constant throughout runtime.</p> <p>When resuming from hibernation, the restore kernel allocates a second memory buffer and reprograms the HFI hardware with the new location as part of a normal boot. The location of the second memory buffer may differ from the one allocated by the image kernel.</p> <p>When the restore kernel transfers control to the image kernel, its HFI buffer becomes invalid, potentially leading to memory corruption if the hardware writes to it (the hardware continues to use the buffer from the restore kernel).</p> <p>It is also possible that the hardware &#34;forgets&#34; the address of the memory buffer when resuming from &#34;deep&#34; suspend. Memory corruption may also occur in such a scenario.</p> <p>To prevent the described memory corruption, disable HFI when preparing to suspend or hibernate. Enable it when resuming.</p> <p>Add syscore callbacks to handle the package of the boot CPU (packages of non-boot CPUs are handled via CPU offline). Syscore ops always run on the boot CPU. Additionally, HFI only needs to be disabled during &#34;deep&#34; suspend and hibernation. Syscore ops only run in these cases.</p> <p>[ rjw: Comment adjustment, subject and changelog edits ]</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>thermal: intel: hfi: Add syscore callbacks for system-wide PM</p> <p>The kernel allocates a memory buffer and provides its location to the hardware, which uses it to update the HFI table. This allocation occurs during boot and remains constant throughout runtime.</p> <p>When resuming from hibernation, the restore kernel allocates a second memory buffer and reprograms the HFI hardware with the new location as part of a normal boot. The location of the second memory buffer may differ from the one allocated by the image kernel.</p> <p>When the restore kernel transfers control to the image kernel, its HFI buffer becomes invalid, potentially leading to memory corruption if the hardware writes to it (the hardware continues to use the buffer from the restore kernel).</p> <p>It is also possible that the hardware &#34;forgets&#34; the address of the memory buffer when resuming from &#34;deep&#34; suspend. Memory corruption may also occur in such a scenario.</p> <p>To prevent the described memory corruption, disable HFI when preparing to suspend or hibernate. Enable it when resuming.</p> <p>Add syscore callbacks to handle the package of the boot CPU (packages of non-boot CPUs are handled via CPU offline). Syscore ops always run on the boot CPU. Additionally, HFI only needs to be disabled during &#34;deep&#34; suspend and hibernation. Syscore ops only run in these cases.</p> <p>[ rjw: Comment adjustment, subject and changelog edits ]</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-26646 https://cve.radiocsirt.org/vuln/ghsa-wrwp-f8pq-q3qj <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>thermal: intel: hfi: Add syscore callbacks for system-wide PM</p> <p>The kernel allocates a memory buffer and provides its location to the hardware, which uses it to update the HFI table. This allocation occurs during boot and remains constant throughout runtime.</p> <p>When resuming from hibernation, the restore kernel allocates a second memory buffer and reprograms the HFI hardware with the new location as part of a normal boot. The location of the second memory buffer may differ from the one allocated by the image kernel.</p> <p>When the restore kernel transfers control to the image kernel, its HFI buffer becomes invalid, potentially leading to memory corruption if the hardware writes to it (the hardware continues to use the buffer from the restore kernel).</p> <p>It is also possible that the hardware &#34;forgets&#34; the address of the memory buffer when resuming from &#34;deep&#34; suspend. Memory corruption may also occur in such a scenario.</p> <p>To prevent the described memory corruption, disable HFI when preparing to suspend or hibernate. Enable it when resuming.</p> <p>Add syscore callbacks to handle the package of the boot CPU (packages of non-boot CPUs are handled via CPU offline). Syscore ops always run on the boot CPU. Additionally, HFI only needs to be disabled during &#34;deep&#34; suspend and hibernation. Syscore ops only run in these cases.</p> <p>[ rjw: Comment adjustment, subject and changelog edits ]</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>thermal: intel: hfi: Add syscore callbacks for system-wide PM</p> <p>The kernel allocates a memory buffer and provides its location to the hardware, which uses it to update the HFI table. This allocation occurs during boot and remains constant throughout runtime.</p> <p>When resuming from hibernation, the restore kernel allocates a second memory buffer and reprograms the HFI hardware with the new location as part of a normal boot. The location of the second memory buffer may differ from the one allocated by the image kernel.</p> <p>When the restore kernel transfers control to the image kernel, its HFI buffer becomes invalid, potentially leading to memory corruption if the hardware writes to it (the hardware continues to use the buffer from the restore kernel).</p> <p>It is also possible that the hardware &#34;forgets&#34; the address of the memory buffer when resuming from &#34;deep&#34; suspend. Memory corruption may also occur in such a scenario.</p> <p>To prevent the described memory corruption, disable HFI when preparing to suspend or hibernate. Enable it when resuming.</p> <p>Add syscore callbacks to handle the package of the boot CPU (packages of non-boot CPUs are handled via CPU offline). Syscore ops always run on the boot CPU. Additionally, HFI only needs to be disabled during &#34;deep&#34; suspend and hibernation. Syscore ops only run in these cases.</p> <p>[ rjw: Comment adjustment, subject and changelog edits ]</p> https://cve.radiocsirt.org/vuln/ghsa-wrwp-f8pq-q3qj https://cve.radiocsirt.org/vuln/gsd-2024-26646 gsd-2024-26646 https://cve.radiocsirt.org/vuln/gsd-2024-26646 https://cve.radiocsirt.org/vuln/msrc_cve-2024-26646 msrc_CVE-2024-26646 https://cve.radiocsirt.org/vuln/msrc_cve-2024-26646 https://cve.radiocsirt.org/vuln/rhsa-2024:9315 <p>kernel: use after free in i2c kernel: bluetooth: BR/EDR Bluetooth Impersonation Attacks (BIAS) kernel: hwmon: (lm90) Prevent integer overflow/underflow in hysteresis calculations kernel: asix: fix uninit-value in asix_mdio_read() kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field kernel: powerpc/64s: fix program check interrupt emergency stack path kernel: powerpc/64s: Fix unrecoverable MCE calling async handler from NMI kernel: lib/generic-radix-tree.c: Don&#39;t overflow in peek() kernel: powerpc/smp: do not decrement idle task preempt count in CPU offline kernel: can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible() kernel: usbnet: sanity check for maxpacket kernel: nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells kernel: aio: fix use-after-free due to missing POLLFREE handling kernel: powerpc/pseries: Fix potential memleak in papr_get_attr() kernel: of: fdt: fix off-by-one error in unflatten_dt_nodes() kernel: thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR kernel: vt_ioctl: fix array_index_nospec in vt_setactivate kernel: bpf: Fix crash due to out of bounds access into reg2btf_ids. kernel: lz4: fix LZ4_decompress_safe_partial read out of bound kernel: x86/mce: Work around an erratum on fast string copy instructions…</p> <p>kernel: use after free in i2c kernel: bluetooth: BR/EDR Bluetooth Impersonation Attacks (BIAS) kernel: hwmon: (lm90) Prevent integer overflow/underflow in hysteresis calculations kernel: asix: fix uninit-value in asix_mdio_read() kernel: tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc kernel: hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field kernel: hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field kernel: powerpc/64s: fix program check interrupt emergency stack path kernel: powerpc/64s: Fix unrecoverable MCE calling async handler from NMI kernel: lib/generic-radix-tree.c: Don&#39;t overflow in peek() kernel: powerpc/smp: do not decrement idle task preempt count in CPU offline kernel: can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible() kernel: usbnet: sanity check for maxpacket kernel: nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells kernel: aio: fix use-after-free due to missing POLLFREE handling kernel: powerpc/pseries: Fix potential memleak in papr_get_attr() kernel: of: fdt: fix off-by-one error in unflatten_dt_nodes() kernel: thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR kernel: vt_ioctl: fix array_index_nospec in vt_setactivate kernel: bpf: Fix crash due to out of bounds access into reg2btf_ids. kernel: lz4: fix LZ4_decompress_safe_partial read out of bound kernel: x86/mce: Work around an erratum on fast string copy instructions…</p> https://cve.radiocsirt.org/vuln/rhsa-2024:9315 https://cve.radiocsirt.org/vuln/suse-su-2024:1466-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2024:1466-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26646 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 66 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: thermal: intel: hfi: Add syscore callbacks for system-wide PM The kernel allocates a memory buffer and provides its location to the hardware, which uses it to update the HFI table. This allocation occurs during boot and remains constant throughout runtime. When resuming from hibernation, the restore kernel allocates a second memory buffer and reprograms the HFI hardware with the new location as part of a normal boot. The location of the second memory buffer may differ from the one allocated by the image kernel. When the restore kernel transfers control to the image kernel, its HFI buffer becomes invalid, potentially leading to memory corruption if the hardware writes to it (the hardware continues to use the buffer from the restore kernel). It is also possible that the hardware &#34;forgets&#34; the address of the memory buffer when resuming from &#34;deep&#34; suspend. Memory corruption may also occur in such a scenario. To prevent the described memory corruption, disable HFI when preparing to suspend or hibernate. Enable it when resuming. Add syscore callbacks to handle the package of the boot CPU (packages of non-boot CPUs are handled via CPU offline). Syscore ops always run on the boot CPU. Additionally, HFI only needs to be disabled during &#34;deep&#34; suspend and hibernation. Syscore ops only run in these cases. [ rjw: Comment adjustment, subject and changelog edits ]</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 66 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: thermal: intel: hfi: Add syscore callbacks for system-wide PM The kernel allocates a memory buffer and provides its location to the hardware, which uses it to update the HFI table. This allocation occurs during boot and remains constant throughout runtime. When resuming from hibernation, the restore kernel allocates a second memory buffer and reprograms the HFI hardware with the new location as part of a normal boot. The location of the second memory buffer may differ from the one allocated by the image kernel. When the restore kernel transfers control to the image kernel, its HFI buffer becomes invalid, potentially leading to memory corruption if the hardware writes to it (the hardware continues to use the buffer from the restore kernel). It is also possible that the hardware &#34;forgets&#34; the address of the memory buffer when resuming from &#34;deep&#34; suspend. Memory corruption may also occur in such a scenario. To prevent the described memory corruption, disable HFI when preparing to suspend or hibernate. Enable it when resuming. Add syscore callbacks to handle the package of the boot CPU (packages of non-boot CPUs are handled via CPU offline). Syscore ops always run on the boot CPU. Additionally, HFI only needs to be disabled during &#34;deep&#34; suspend and hibernation. Syscore ops only run in these cases. [ rjw: Comment adjustment, subject and changelog edits ]</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-26646 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0722 <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um Dateien zu manipulieren, unbekannte Effekte zu verursachen oder einen Denial-of-Service-Zustand auszulösen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um Dateien zu manipulieren, unbekannte Effekte zu verursachen oder einen Denial-of-Service-Zustand auszulösen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0722