<?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>Thu, 08 Oct 2026 01:20:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72016 — cpu/hotplug: Fix NULL kobject warning in cpuhp_smt_enable()</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-72016</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;cpu/hotplug: Fix NULL kobject warning in cpuhp_smt_enable()&lt;/p&gt;
&lt;p&gt;On arm64, when booting with `maxcpus` greater than the number of present
CPUs (e.g., QEMU -smp cpus=4,maxcpus=8), some CPUs are marked as &amp;#39;present&amp;#39;
but have not yet been registered via register_cpu(). Consequently,
the per-cpu device objects for these CPUs are not yet initialized.&lt;/p&gt;
&lt;p&gt;In cpuhp_smt_enable(), the code iterates over all present CPUs. Calling
_cpu_up() for these unregistered CPUs eventually leads to
sysfs_create_group() being called with a NULL kobject (or a kobject
without a directory), triggering the following warning in
fs/sysfs/group.c:&lt;/p&gt;
&lt;p&gt;WARNING: fs/sysfs/group.c:137 at internal_create_group+0x41c/0x4bc, CPU#2: sh/181
  [...]
  Call trace:
    internal_create_group+0x41c/0x4bc (P)
    sysfs_create_group+0x18/0x24
    topology_add_dev+0x1c/0x28
    cpuhp_invoke_callback+0x104/0x20c
    __cpuhp_invoke_callback_range+0x94/0x11c
    _cpu_up+0x200/0x37c&lt;/p&gt;
&lt;p&gt;When booting with ACPI, arm64 smp_prepare_cpus() currently sets all
enumerated CPUs as &amp;#34;present&amp;#34; regardless of their status in the MADT. This
causes issues with SMT hotplug control. For instance, with QEMU&amp;#39;s
&amp;#34;-smp 4,maxcpus=8&amp;#34; configuration, the MADT GICC entries are populated as
follows:&lt;/p&gt;
&lt;p&gt;1. The first four CPUs: `Enabled` set but `Online Capable` not set.&lt;/p&gt;
&lt;p&gt;2. The remaining four CPUs: `Online Capable` set but `Enabled` not set
   to support potential hot-plugging.&lt;/p&gt;
&lt;p&gt;Fix this by:&lt;/p&gt;
&lt;p&gt;1. When…&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;cpu/hotplug: Fix NULL kobject warning in cpuhp_smt_enable()&lt;/p&gt;
&lt;p&gt;On arm64, when booting with `maxcpus` greater than the number of present
CPUs (e.g., QEMU -smp cpus=4,maxcpus=8), some CPUs are marked as &amp;#39;present&amp;#39;
but have not yet been registered via register_cpu(). Consequently,
the per-cpu device objects for these CPUs are not yet initialized.&lt;/p&gt;
&lt;p&gt;In cpuhp_smt_enable(), the code iterates over all present CPUs. Calling
_cpu_up() for these unregistered CPUs eventually leads to
sysfs_create_group() being called with a NULL kobject (or a kobject
without a directory), triggering the following warning in
fs/sysfs/group.c:&lt;/p&gt;
&lt;p&gt;WARNING: fs/sysfs/group.c:137 at internal_create_group+0x41c/0x4bc, CPU#2: sh/181
  [...]
  Call trace:
    internal_create_group+0x41c/0x4bc (P)
    sysfs_create_group+0x18/0x24
    topology_add_dev+0x1c/0x28
    cpuhp_invoke_callback+0x104/0x20c
    __cpuhp_invoke_callback_range+0x94/0x11c
    _cpu_up+0x200/0x37c&lt;/p&gt;
&lt;p&gt;When booting with ACPI, arm64 smp_prepare_cpus() currently sets all
enumerated CPUs as &amp;#34;present&amp;#34; regardless of their status in the MADT. This
causes issues with SMT hotplug control. For instance, with QEMU&amp;#39;s
&amp;#34;-smp 4,maxcpus=8&amp;#34; configuration, the MADT GICC entries are populated as
follows:&lt;/p&gt;
&lt;p&gt;1. The first four CPUs: `Enabled` set but `Online Capable` not set.&lt;/p&gt;
&lt;p&gt;2. The remaining four CPUs: `Online Capable` set but `Enabled` not set
   to support potential hot-plugging.&lt;/p&gt;
&lt;p&gt;Fix this by:&lt;/p&gt;
&lt;p&gt;1. When…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-72016</guid>
    </item>
    <item>
      <title>USN-8887-1 — linux, linux-aws, linux-gcp, linux-gke, linux-ibm, linux-oracle, linux-realtime vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8887-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-gke, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle, Ubuntu:26.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD processors did not properly perform Reverse
Map Table (RMP) checks when the IOMMU accessed certain host buffers. A
local attacker with hypervisor access could possibly use this to trigger an
out-of-bounds condition and compromise the integrity of SEV-SNP guest
memory. (CVE-2023-20585)&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;
  - NVDIMM (Non-Volatile Memory Device) drivers;
  - Handshake API;
  - ARM32 architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - ACPI drivers;
  - Android drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Rados block device (RBD) driver;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - Cdrom driver;
  - Character device driver;
  - TPM device driver;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - DIBS (Direct Internal Buffer Sharing) drivers;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - DPLL subsystem;
  - EDAC drivers;
  - FireWire subsystem;
  - Arm Firmware Framework fo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-gke, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle, Ubuntu:26.04:LTS: linux-realtime&lt;/p&gt;
&lt;p&gt;It was discovered that some AMD processors did not properly perform Reverse
Map Table (RMP) checks when the IOMMU accessed certain host buffers. A
local attacker with hypervisor access could possibly use this to trigger an
out-of-bounds condition and compromise the integrity of SEV-SNP guest
memory. (CVE-2023-20585)&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;
  - NVDIMM (Non-Volatile Memory Device) drivers;
  - Handshake API;
  - ARM32 architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - ACPI drivers;
  - Android drivers;
  - Serial ATA and Parallel ATA drivers;
  - Drivers core;
  - Rados block device (RBD) driver;
  - Ublk userspace block driver;
  - Bluetooth drivers;
  - Cdrom driver;
  - Character device driver;
  - TPM device driver;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - DIBS (Direct Internal Buffer Sharing) drivers;
  - Buffer Sharing and Synchronization framework;
  - DMA engine subsystem;
  - DPLL subsystem;
  - EDAC drivers;
  - FireWire subsystem;
  - Arm Firmware Framework fo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8887-1</guid>
    </item>
  </channel>
</rss>
