<?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://vulnerability.circl.lu</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>Mon, 12 Oct 2026 13:10:21 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98259</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-98259</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-98259</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98259</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-98259</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/dax: check zero or empty entry before converting xarray entry&lt;/p&gt;
&lt;p&gt;Calling dax_to_folio() with empty entry causes kernel panic below when
booting a VM with DAX enabled storage.&lt;/p&gt;
&lt;p&gt;This patch checks empty entry before calling dax_to_folio() on
dax_associate_entry(), dax_disassociate_entry(), and dax_busy_page().&lt;/p&gt;
&lt;p&gt;Commit 98c183a4fccf (&amp;#34;fs/dax: don&amp;#39;t disassociate zero page entries&amp;#34;) added
guards in the associate and disassociate paths, but the guards still come
after dax_to_folio(), and dax_busy_page() still has the same problem.&lt;/p&gt;
&lt;p&gt;[    0.737679] EXT4-fs (pmem0p1): mounted filesystem 79676804-7c8b-491a-b2a6-9bae3c72af70 ro with ordered data mode. Quota mode: disabled.
[    0.737891] VFS: Mounted root (ext4 filesystem) readonly on device 259:1.
[    0.739119] devtmpfs: mounted
[    0.739476] Freeing unused kernel memory: 1920K
[    0.740156] Run /sbin/init as init process
[    0.740229]   with arguments:
[    0.740286]     /sbin/init
[    0.740321]   with environment:
[    0.740369]     HOME=/
[    0.740400]     TERM=linux
[    0.743162] Unable to handle kernel paging request at virtual address fffffdffbf000008
[    0.743285] Mem abort info:
[    0.743316]   ESR = 0x0000000096000006
[    0.743371]   EC = 0x25: DABT (current EL), IL = 32 bits
[    0.743444]   SET = 0, FnV = 0
[    0.743489]   EA = 0, S1PTW = 0
[    0.743545]   FSC = 0x06: level 2 translation fault
[    0.743610] Data abort info:
[    0.743656]   ISV…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/dax: check zero or empty entry before converting xarray entry&lt;/p&gt;
&lt;p&gt;Calling dax_to_folio() with empty entry causes kernel panic below when
booting a VM with DAX enabled storage.&lt;/p&gt;
&lt;p&gt;This patch checks empty entry before calling dax_to_folio() on
dax_associate_entry(), dax_disassociate_entry(), and dax_busy_page().&lt;/p&gt;
&lt;p&gt;Commit 98c183a4fccf (&amp;#34;fs/dax: don&amp;#39;t disassociate zero page entries&amp;#34;) added
guards in the associate and disassociate paths, but the guards still come
after dax_to_folio(), and dax_busy_page() still has the same problem.&lt;/p&gt;
&lt;p&gt;[    0.737679] EXT4-fs (pmem0p1): mounted filesystem 79676804-7c8b-491a-b2a6-9bae3c72af70 ro with ordered data mode. Quota mode: disabled.
[    0.737891] VFS: Mounted root (ext4 filesystem) readonly on device 259:1.
[    0.739119] devtmpfs: mounted
[    0.739476] Freeing unused kernel memory: 1920K
[    0.740156] Run /sbin/init as init process
[    0.740229]   with arguments:
[    0.740286]     /sbin/init
[    0.740321]   with environment:
[    0.740369]     HOME=/
[    0.740400]     TERM=linux
[    0.743162] Unable to handle kernel paging request at virtual address fffffdffbf000008
[    0.743285] Mem abort info:
[    0.743316]   ESR = 0x0000000096000006
[    0.743371]   EC = 0x25: DABT (current EL), IL = 32 bits
[    0.743444]   SET = 0, FnV = 0
[    0.743489]   EA = 0, S1PTW = 0
[    0.743545]   FSC = 0x06: level 2 translation fault
[    0.743610] Data abort info:
[    0.743656]   ISV…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-98259</guid>
    </item>
    <item>
      <title>GHSA-4mxc-9hcf-g45q</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-4mxc-9hcf-g45q</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/dax: check zero or empty entry before converting xarray entry&lt;/p&gt;
&lt;p&gt;Calling dax_to_folio() with empty entry causes kernel panic below when
booting a VM with DAX enabled storage.&lt;/p&gt;
&lt;p&gt;This patch checks empty entry before calling dax_to_folio() on
dax_associate_entry(), dax_disassociate_entry(), and dax_busy_page().&lt;/p&gt;
&lt;p&gt;Commit 98c183a4fccf (&amp;#34;fs/dax: don&amp;#39;t disassociate zero page entries&amp;#34;) added
guards in the associate and disassociate paths, but the guards still come
after dax_to_folio(), and dax_busy_page() still has the same problem.&lt;/p&gt;
&lt;p&gt;[    0.737679] EXT4-fs (pmem0p1): mounted filesystem 79676804-7c8b-491a-b2a6-9bae3c72af70 ro with ordered data mode. Quota mode: disabled.
[    0.737891] VFS: Mounted root (ext4 filesystem) readonly on device 259:1.
[    0.739119] devtmpfs: mounted
[    0.739476] Freeing unused kernel memory: 1920K
[    0.740156] Run /sbin/init as init process
[    0.740229]   with arguments:
[    0.740286]     /sbin/init
[    0.740321]   with environment:
[    0.740369]     HOME=/
[    0.740400]     TERM=linux
[    0.743162] Unable to handle kernel paging request at virtual address fffffdffbf000008
[    0.743285] Mem abort info:
[    0.743316]   ESR = 0x0000000096000006
[    0.743371]   EC = 0x25: DABT (current EL), IL = 32 bits
[    0.743444]   SET = 0, FnV = 0
[    0.743489]   EA = 0, S1PTW = 0
[    0.743545]   FSC = 0x06: level 2 translation fault
[    0.743610] Data abort info:
[    0.743656]   ISV…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;fs/dax: check zero or empty entry before converting xarray entry&lt;/p&gt;
&lt;p&gt;Calling dax_to_folio() with empty entry causes kernel panic below when
booting a VM with DAX enabled storage.&lt;/p&gt;
&lt;p&gt;This patch checks empty entry before calling dax_to_folio() on
dax_associate_entry(), dax_disassociate_entry(), and dax_busy_page().&lt;/p&gt;
&lt;p&gt;Commit 98c183a4fccf (&amp;#34;fs/dax: don&amp;#39;t disassociate zero page entries&amp;#34;) added
guards in the associate and disassociate paths, but the guards still come
after dax_to_folio(), and dax_busy_page() still has the same problem.&lt;/p&gt;
&lt;p&gt;[    0.737679] EXT4-fs (pmem0p1): mounted filesystem 79676804-7c8b-491a-b2a6-9bae3c72af70 ro with ordered data mode. Quota mode: disabled.
[    0.737891] VFS: Mounted root (ext4 filesystem) readonly on device 259:1.
[    0.739119] devtmpfs: mounted
[    0.739476] Freeing unused kernel memory: 1920K
[    0.740156] Run /sbin/init as init process
[    0.740229]   with arguments:
[    0.740286]     /sbin/init
[    0.740321]   with environment:
[    0.740369]     HOME=/
[    0.740400]     TERM=linux
[    0.743162] Unable to handle kernel paging request at virtual address fffffdffbf000008
[    0.743285] Mem abort info:
[    0.743316]   ESR = 0x0000000096000006
[    0.743371]   EC = 0x25: DABT (current EL), IL = 32 bits
[    0.743444]   SET = 0, FnV = 0
[    0.743489]   EA = 0, S1PTW = 0
[    0.743545]   FSC = 0x06: level 2 translation fault
[    0.743610] Data abort info:
[    0.743656]   ISV…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-4mxc-9hcf-g45q</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98259</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98259</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fs/dax: check zero or empty entry before converting xarray entry Calling dax_to_folio() with empty entry causes kernel panic below when booting a VM with DAX enabled storage. This patch checks empty entry before calling dax_to_folio() on dax_associate_entry(), dax_disassociate_entry(), and dax_busy_page(). Commit 98c183a4fccf (&amp;#34;fs/dax: don&amp;#39;t disassociate zero page entries&amp;#34;) added guards in the associate and disassociate paths, but the guards still come after dax_to_folio(), and dax_busy_page() still has the same problem. [    0.737679] EXT4-fs (pmem0p1): mounted filesystem 79676804-7c8b-491a-b2a6-9bae3c72af70 ro with ordered data mode. Quota mode: disabled. [    0.737891] VFS: Mounted root (ext4 filesystem) readonly on device 259:1. [    0.739119] devtmpfs: mounted [    0.739476] Freeing unused kernel memory: 1920K [    0.740156] Run /sbin/init as init process [    0.740229]   with arguments: [    0.740286]     /sbin/init [    0.740321]   with environment: [    0.740369]     HOME=/ [    0.740400]     TERM=linux [    0.743162] Unable to handle kernel paging request at virtual address fffffdffbf000008 [    0.743285] Mem abort info: [    0.743316]   ESR = 0x0000000096000006 [    0.743371]   EC = 0x25: DABT (current EL), IL = 32 bits [    0.743444]   SET = 0, FnV = 0 [    0.743489]   EA = 0, S1PTW = 0 [    0.743545]   FSC = 0x06: level 2 translation fault [    0.743610] Data abort info: [    0.743656]   ISV = 0,…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: fs/dax: check zero or empty entry before converting xarray entry Calling dax_to_folio() with empty entry causes kernel panic below when booting a VM with DAX enabled storage. This patch checks empty entry before calling dax_to_folio() on dax_associate_entry(), dax_disassociate_entry(), and dax_busy_page(). Commit 98c183a4fccf (&amp;#34;fs/dax: don&amp;#39;t disassociate zero page entries&amp;#34;) added guards in the associate and disassociate paths, but the guards still come after dax_to_folio(), and dax_busy_page() still has the same problem. [    0.737679] EXT4-fs (pmem0p1): mounted filesystem 79676804-7c8b-491a-b2a6-9bae3c72af70 ro with ordered data mode. Quota mode: disabled. [    0.737891] VFS: Mounted root (ext4 filesystem) readonly on device 259:1. [    0.739119] devtmpfs: mounted [    0.739476] Freeing unused kernel memory: 1920K [    0.740156] Run /sbin/init as init process [    0.740229]   with arguments: [    0.740286]     /sbin/init [    0.740321]   with environment: [    0.740369]     HOME=/ [    0.740400]     TERM=linux [    0.743162] Unable to handle kernel paging request at virtual address fffffdffbf000008 [    0.743285] Mem abort info: [    0.743316]   ESR = 0x0000000096000006 [    0.743371]   EC = 0x25: DABT (current EL), IL = 32 bits [    0.743444]   SET = 0, FnV = 0 [    0.743489]   EA = 0, S1PTW = 0 [    0.743545]   FSC = 0x06: level 2 translation fault [    0.743610] Data abort info: [    0.743656]   ISV = 0,…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98259</guid>
    </item>
  </channel>
</rss>
