<?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 01:35:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23097 — migrate: correct lock ordering for hugetlb file folios</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-23097</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;migrate: correct lock ordering for hugetlb file folios&lt;/p&gt;
&lt;p&gt;Syzbot has found a deadlock (analyzed by Lance Yang):&lt;/p&gt;
&lt;p&gt;1) Task (5749): Holds folio_lock, then tries to acquire i_mmap_rwsem(read lock).
2) Task (5754): Holds i_mmap_rwsem(write lock), then tries to acquire
folio_lock.&lt;/p&gt;
&lt;p&gt;migrate_pages()
  -&amp;gt; migrate_hugetlbs()
    -&amp;gt; unmap_and_move_huge_page()     &amp;lt;- Takes folio_lock!
      -&amp;gt; remove_migration_ptes()
        -&amp;gt; __rmap_walk_file()
          -&amp;gt; i_mmap_lock_read()       &amp;lt;- Waits for i_mmap_rwsem(read lock)!&lt;/p&gt;
&lt;p&gt;hugetlbfs_fallocate()
  -&amp;gt; hugetlbfs_punch_hole()           &amp;lt;- Takes i_mmap_rwsem(write lock)!
    -&amp;gt; hugetlbfs_zero_partial_page()
     -&amp;gt; filemap_lock_hugetlb_folio()
      -&amp;gt; filemap_lock_folio()
        -&amp;gt; __filemap_get_folio        &amp;lt;- Waits for folio_lock!&lt;/p&gt;
&lt;p&gt;The migration path is the one taking locks in the wrong order according to
the documentation at the top of mm/rmap.c.  So expand the scope of the
existing i_mmap_lock to cover the calls to remove_migration_ptes() too.&lt;/p&gt;
&lt;p&gt;This is (mostly) how it used to be after commit c0d0381ade79.  That was
removed by 336bf30eb765 for both file &amp;amp; anon hugetlb pages when it should
only have been removed for anon hugetlb pages.&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;migrate: correct lock ordering for hugetlb file folios&lt;/p&gt;
&lt;p&gt;Syzbot has found a deadlock (analyzed by Lance Yang):&lt;/p&gt;
&lt;p&gt;1) Task (5749): Holds folio_lock, then tries to acquire i_mmap_rwsem(read lock).
2) Task (5754): Holds i_mmap_rwsem(write lock), then tries to acquire
folio_lock.&lt;/p&gt;
&lt;p&gt;migrate_pages()
  -&amp;gt; migrate_hugetlbs()
    -&amp;gt; unmap_and_move_huge_page()     &amp;lt;- Takes folio_lock!
      -&amp;gt; remove_migration_ptes()
        -&amp;gt; __rmap_walk_file()
          -&amp;gt; i_mmap_lock_read()       &amp;lt;- Waits for i_mmap_rwsem(read lock)!&lt;/p&gt;
&lt;p&gt;hugetlbfs_fallocate()
  -&amp;gt; hugetlbfs_punch_hole()           &amp;lt;- Takes i_mmap_rwsem(write lock)!
    -&amp;gt; hugetlbfs_zero_partial_page()
     -&amp;gt; filemap_lock_hugetlb_folio()
      -&amp;gt; filemap_lock_folio()
        -&amp;gt; __filemap_get_folio        &amp;lt;- Waits for folio_lock!&lt;/p&gt;
&lt;p&gt;The migration path is the one taking locks in the wrong order according to
the documentation at the top of mm/rmap.c.  So expand the scope of the
existing i_mmap_lock to cover the calls to remove_migration_ptes() too.&lt;/p&gt;
&lt;p&gt;This is (mostly) how it used to be after commit c0d0381ade79.  That was
removed by 336bf30eb765 for both file &amp;amp; anon hugetlb pages when it should
only have been removed for anon hugetlb pages.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-23097</guid>
    </item>
    <item>
      <title>USN-8162-1 — linux-nvidia-tegra-5.15 vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-8162-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: linux-nvidia-tegra-5.15&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;
  - Block layer subsystem;
  - Cryptographic API;
  - Drivers core;
  - Bluetooth drivers;
  - DMA engine subsystem;
  - GPU drivers;
  - HID subsystem;
  - Intel Trace Hub HW tracing drivers;
  - IIO ADC drivers;
  - IRQ chip drivers;
  - Modular ISDN driver;
  - LED subsystem;
  - UACCE accelerator framework;
  - Ethernet bonding driver;
  - Network drivers;
  - STMicroelectronics network drivers;
  - Ethernet team driver;
  - NVME drivers;
  - PHY drivers;
  - SLIMbus drivers;
  - W1 Dallas&amp;#39;s 1-wire bus driver;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ext4 file system;
  - Network file system (NFS) client;
  - Network file system (NFS) server daemon;
  - NTFS3 file system;
  - SMB network file system;
  - NFC subsystem;
  - BPF subsystem;
  - IRQ subsystem;
  - Memory management;
  - Bluetooth subsystem;
  - CAN network layer;
  - Networking core;
  - IPv4 networking;
  - IPv6 networking;
  - L2TP protocol;
  - Netfilter;
  - NET/ROM layer;
  - Network traffic control;
  - SCTP protocol;
  - TLS protocol;
  - XFRM subsystem;
  - Creative Sound Blaster X-Fi driver;
  - USB sound devices;
(CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207,
CVE-2025-37849, CVE-2025-38057, CVE-2025-38125, CVE-2025-38232,
CVE-2025-38408, CVE-2025-38591, CVE-2025-4014…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: linux-nvidia-tegra-5.15&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;
  - Block layer subsystem;
  - Cryptographic API;
  - Drivers core;
  - Bluetooth drivers;
  - DMA engine subsystem;
  - GPU drivers;
  - HID subsystem;
  - Intel Trace Hub HW tracing drivers;
  - IIO ADC drivers;
  - IRQ chip drivers;
  - Modular ISDN driver;
  - LED subsystem;
  - UACCE accelerator framework;
  - Ethernet bonding driver;
  - Network drivers;
  - STMicroelectronics network drivers;
  - Ethernet team driver;
  - NVME drivers;
  - PHY drivers;
  - SLIMbus drivers;
  - W1 Dallas&amp;#39;s 1-wire bus driver;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ext4 file system;
  - Network file system (NFS) client;
  - Network file system (NFS) server daemon;
  - NTFS3 file system;
  - SMB network file system;
  - NFC subsystem;
  - BPF subsystem;
  - IRQ subsystem;
  - Memory management;
  - Bluetooth subsystem;
  - CAN network layer;
  - Networking core;
  - IPv4 networking;
  - IPv6 networking;
  - L2TP protocol;
  - Netfilter;
  - NET/ROM layer;
  - Network traffic control;
  - SCTP protocol;
  - TLS protocol;
  - XFRM subsystem;
  - Creative Sound Blaster X-Fi driver;
  - USB sound devices;
(CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207,
CVE-2025-37849, CVE-2025-38057, CVE-2025-38125, CVE-2025-38232,
CVE-2025-38408, CVE-2025-38591, CVE-2025-4014…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-8162-1</guid>
    </item>
  </channel>
</rss>
