<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 16 Oct 2026 09:30:41 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-26646 — thermal: intel: hfi: Add syscore callbacks for system-wide PM</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-26646</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;thermal: intel: hfi: Add syscore callbacks for system-wide PM&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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).&lt;/p&gt;
&lt;p&gt;It is also possible that the hardware &amp;#34;forgets&amp;#34; the address of the memory
buffer when resuming from &amp;#34;deep&amp;#34; suspend. Memory corruption may also occur
in such a scenario.&lt;/p&gt;
&lt;p&gt;To prevent the described memory corruption, disable HFI when preparing to
suspend or hibernate. Enable it when resuming.&lt;/p&gt;
&lt;p&gt;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 &amp;#34;deep&amp;#34; suspend
and hibernation. Syscore ops only run in these cases.&lt;/p&gt;
&lt;p&gt;[ rjw: Comment adjustment, subject and changelog edits ]&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;thermal: intel: hfi: Add syscore callbacks for system-wide PM&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;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).&lt;/p&gt;
&lt;p&gt;It is also possible that the hardware &amp;#34;forgets&amp;#34; the address of the memory
buffer when resuming from &amp;#34;deep&amp;#34; suspend. Memory corruption may also occur
in such a scenario.&lt;/p&gt;
&lt;p&gt;To prevent the described memory corruption, disable HFI when preparing to
suspend or hibernate. Enable it when resuming.&lt;/p&gt;
&lt;p&gt;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 &amp;#34;deep&amp;#34; suspend
and hibernation. Syscore ops only run in these cases.&lt;/p&gt;
&lt;p&gt;[ rjw: Comment adjustment, subject and changelog edits ]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-26646</guid>
    </item>
    <item>
      <title>USN-6818-1 — linux, linux-gcp, linux-gcp-6.5, linux-lowlatency, linux-lowlatency-hwe-6.5, linux-raspi vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-6818-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-gcp-6.5, Ubuntu:22.04:LTS: linux-lowlatency-hwe-6.5&lt;/p&gt;
&lt;p&gt;Alon Zahavi discovered that the NVMe-oF/TCP subsystem in the Linux kernel
did not properly validate H2C PDU data, leading to a null pointer
dereference vulnerability. A remote attacker could use this to cause a
denial of service (system crash). (CVE-2023-6356, CVE-2023-6535,
CVE-2023-6536)&lt;/p&gt;
&lt;p&gt;It was discovered that the Intel Data Streaming and Intel Analytics
Accelerator drivers in the Linux kernel allowed direct access to the
devices for unprivileged users and virtual machines. A local attacker could
use this to cause a denial of service. (CVE-2024-21823)&lt;/p&gt;
&lt;p&gt;Chenyuan Yang discovered that the RDS Protocol implementation in the Linux
kernel contained an out-of-bounds read vulnerability. An attacker could use
this to possibly cause a denial of service (system crash). (CVE-2024-23849)&lt;/p&gt;
&lt;p&gt;It was discovered that a race condition existed in the Bluetooth subsystem
in the Linux kernel, leading to a null pointer dereference vulnerability. A
privileged local attacker could use this to possibly cause a denial of
service (system crash). (CVE-2024-24860)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - Core kernel;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - Android drivers;
  - Drivers core;
  - Power management…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-gcp-6.5, Ubuntu:22.04:LTS: linux-lowlatency-hwe-6.5&lt;/p&gt;
&lt;p&gt;Alon Zahavi discovered that the NVMe-oF/TCP subsystem in the Linux kernel
did not properly validate H2C PDU data, leading to a null pointer
dereference vulnerability. A remote attacker could use this to cause a
denial of service (system crash). (CVE-2023-6356, CVE-2023-6535,
CVE-2023-6536)&lt;/p&gt;
&lt;p&gt;It was discovered that the Intel Data Streaming and Intel Analytics
Accelerator drivers in the Linux kernel allowed direct access to the
devices for unprivileged users and virtual machines. A local attacker could
use this to cause a denial of service. (CVE-2024-21823)&lt;/p&gt;
&lt;p&gt;Chenyuan Yang discovered that the RDS Protocol implementation in the Linux
kernel contained an out-of-bounds read vulnerability. An attacker could use
this to possibly cause a denial of service (system crash). (CVE-2024-23849)&lt;/p&gt;
&lt;p&gt;It was discovered that a race condition existed in the Bluetooth subsystem
in the Linux kernel, leading to a null pointer dereference vulnerability. A
privileged local attacker could use this to possibly cause a denial of
service (system crash). (CVE-2024-24860)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - Core kernel;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - ACPI drivers;
  - Android drivers;
  - Drivers core;
  - Power management…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-6818-1</guid>
    </item>
  </channel>
</rss>
