<?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>Wed, 14 Oct 2026 20:40:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31600 — arm64: mm: Handle invalid large leaf mappings correctly</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-31600</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;arm64: mm: Handle invalid large leaf mappings correctly&lt;/p&gt;
&lt;p&gt;It has been possible for a long time to mark ptes in the linear map as
invalid. This is done for secretmem, kfence, realm dma memory un/share,
and others, by simply clearing the PTE_VALID bit. But until commit
a166563e7ec37 (&amp;#34;arm64: mm: support large block mapping when
rodata=full&amp;#34;) large leaf mappings were never made invalid in this way.&lt;/p&gt;
&lt;p&gt;It turns out various parts of the code base are not equipped to handle
invalid large leaf mappings (in the way they are currently encoded) and
I&amp;#39;ve observed a kernel panic while booting a realm guest on a
BBML2_NOABORT system as a result:&lt;/p&gt;
&lt;p&gt;[   15.432706] software IO TLB: Memory encryption is active and system is using DMA bounce buffers
[   15.476896] Unable to handle kernel paging request at virtual address ffff000019600000
[   15.513762] Mem abort info:
[   15.527245]   ESR = 0x0000000096000046
[   15.548553]   EC = 0x25: DABT (current EL), IL = 32 bits
[   15.572146]   SET = 0, FnV = 0
[   15.592141]   EA = 0, S1PTW = 0
[   15.612694]   FSC = 0x06: level 2 translation fault
[   15.640644] Data abort info:
[   15.661983]   ISV = 0, ISS = 0x00000046, ISS2 = 0x00000000
[   15.694875]   CM = 0, WnR = 1, TnD = 0, TagAccess = 0
[   15.723740]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
[   15.755776] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000000081f3f000
[   15.800410] [ffff000019600000] pgd=0000000000000000, p4…&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;arm64: mm: Handle invalid large leaf mappings correctly&lt;/p&gt;
&lt;p&gt;It has been possible for a long time to mark ptes in the linear map as
invalid. This is done for secretmem, kfence, realm dma memory un/share,
and others, by simply clearing the PTE_VALID bit. But until commit
a166563e7ec37 (&amp;#34;arm64: mm: support large block mapping when
rodata=full&amp;#34;) large leaf mappings were never made invalid in this way.&lt;/p&gt;
&lt;p&gt;It turns out various parts of the code base are not equipped to handle
invalid large leaf mappings (in the way they are currently encoded) and
I&amp;#39;ve observed a kernel panic while booting a realm guest on a
BBML2_NOABORT system as a result:&lt;/p&gt;
&lt;p&gt;[   15.432706] software IO TLB: Memory encryption is active and system is using DMA bounce buffers
[   15.476896] Unable to handle kernel paging request at virtual address ffff000019600000
[   15.513762] Mem abort info:
[   15.527245]   ESR = 0x0000000096000046
[   15.548553]   EC = 0x25: DABT (current EL), IL = 32 bits
[   15.572146]   SET = 0, FnV = 0
[   15.592141]   EA = 0, S1PTW = 0
[   15.612694]   FSC = 0x06: level 2 translation fault
[   15.640644] Data abort info:
[   15.661983]   ISV = 0, ISS = 0x00000046, ISS2 = 0x00000000
[   15.694875]   CM = 0, WnR = 1, TnD = 0, TagAccess = 0
[   15.723740]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
[   15.755776] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000000081f3f000
[   15.800410] [ffff000019600000] pgd=0000000000000000, p4…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-31600</guid>
    </item>
    <item>
      <title>USN-8488-1 — linux, linux-aws, linux-gcp, linux-ibm, linux-oracle, linux-realtime vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8488-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-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 clear data in
the floating point divider unit during speculative execution. A local
attacker could use this to expose sensitive information. (CVE-2025-54505)&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;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Rados block device (RBD) driver;
  - Compressed RAM block device driver;
  - Character device driver;
  - TPM device driver;
  - Hardware crypto device drivers;
  - EDAC drivers;
  - GPU drivers;
  - Greybus drivers;
  - HID subsystem;
  - Microsoft Hyper-V drivers;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - IBM Advanced System Management driver;
  - MTD block device drivers;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - NTB driver;
  - NVME drivers;
  - Device tree and open firmware driver;
  - PCI subsystem;
  - Remote Processor subsystem;
  - SCSI subsystem;
  - SPI subsystem;
  - Realtek RTL8723BS SDIO drivers;
  - SM750 framebuffer staging driver;
  - Thermal drivers;
  - USB Gadget drivers;
  - USB over IP driver;
  - VFIO drivers;
  - Framebuffer layer;
  - 9P distributed file system;
  - AFS file…&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-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 clear data in
the floating point divider unit during speculative execution. A local
attacker could use this to expose sensitive information. (CVE-2025-54505)&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;
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Rados block device (RBD) driver;
  - Compressed RAM block device driver;
  - Character device driver;
  - TPM device driver;
  - Hardware crypto device drivers;
  - EDAC drivers;
  - GPU drivers;
  - Greybus drivers;
  - HID subsystem;
  - Microsoft Hyper-V drivers;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - IBM Advanced System Management driver;
  - MTD block device drivers;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - NTB driver;
  - NVME drivers;
  - Device tree and open firmware driver;
  - PCI subsystem;
  - Remote Processor subsystem;
  - SCSI subsystem;
  - SPI subsystem;
  - Realtek RTL8723BS SDIO drivers;
  - SM750 framebuffer staging driver;
  - Thermal drivers;
  - USB Gadget drivers;
  - USB over IP driver;
  - VFIO drivers;
  - Framebuffer layer;
  - 9P distributed file system;
  - AFS file…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8488-1</guid>
    </item>
  </channel>
</rss>
