<?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, 05 Oct 2026 04:07:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-26785 — iommufd: Fix protection fault in iommufd_test_syz_conv_iova</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-26785</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;iommufd: Fix protection fault in iommufd_test_syz_conv_iova&lt;/p&gt;
&lt;p&gt;Syzkaller reported the following bug:&lt;/p&gt;
&lt;p&gt;general protection fault, probably for non-canonical address 0xdffffc0000000038: 0000 [#1] SMP KASAN
  KASAN: null-ptr-deref in range [0x00000000000001c0-0x00000000000001c7]
  Call Trace:
   lock_acquire
   lock_acquire+0x1ce/0x4f0
   down_read+0x93/0x4a0
   iommufd_test_syz_conv_iova+0x56/0x1f0
   iommufd_test_access_rw.isra.0+0x2ec/0x390
   iommufd_test+0x1058/0x1e30
   iommufd_fops_ioctl+0x381/0x510
   vfs_ioctl
   __do_sys_ioctl
   __se_sys_ioctl
   __x64_sys_ioctl+0x170/0x1e0
   do_syscall_x64
   do_syscall_64+0x71/0x140&lt;/p&gt;
&lt;p&gt;This is because the new iommufd_access_change_ioas() sets access-&amp;gt;ioas to
NULL during its process, so the lock might be gone in a concurrent racing
context.&lt;/p&gt;
&lt;p&gt;Fix this by doing the same access-&amp;gt;ioas sanity as iommufd_access_rw() and
iommufd_access_pin_pages() functions do.&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;iommufd: Fix protection fault in iommufd_test_syz_conv_iova&lt;/p&gt;
&lt;p&gt;Syzkaller reported the following bug:&lt;/p&gt;
&lt;p&gt;general protection fault, probably for non-canonical address 0xdffffc0000000038: 0000 [#1] SMP KASAN
  KASAN: null-ptr-deref in range [0x00000000000001c0-0x00000000000001c7]
  Call Trace:
   lock_acquire
   lock_acquire+0x1ce/0x4f0
   down_read+0x93/0x4a0
   iommufd_test_syz_conv_iova+0x56/0x1f0
   iommufd_test_access_rw.isra.0+0x2ec/0x390
   iommufd_test+0x1058/0x1e30
   iommufd_fops_ioctl+0x381/0x510
   vfs_ioctl
   __do_sys_ioctl
   __se_sys_ioctl
   __x64_sys_ioctl+0x170/0x1e0
   do_syscall_x64
   do_syscall_64+0x71/0x140&lt;/p&gt;
&lt;p&gt;This is because the new iommufd_access_change_ioas() sets access-&amp;gt;ioas to
NULL during its process, so the lock might be gone in a concurrent racing
context.&lt;/p&gt;
&lt;p&gt;Fix this by doing the same access-&amp;gt;ioas sanity as iommufd_access_rw() and
iommufd_access_pin_pages() functions do.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-26785</guid>
    </item>
  </channel>
</rss>
