<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 13:50:38 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38722</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38722</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2025-38722</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0895 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0895</link>
      <description>certfr-2025-avi-0895</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0895</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38722</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38722</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 124 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: habanalabs: fix UAF in export_dmabuf() As soon as we&amp;#39;d inserted a file reference into descriptor table, another thread could close it.  That&amp;#39;s fine for the case when all we are doing is returning that descriptor to userland (it&amp;#39;s a race, but it&amp;#39;s a userland race and there&amp;#39;s nothing the kernel can do about it).  However, if we follow fd_install() with any kind of access to objects that would be destroyed on close (be it the struct file itself or anything destroyed by its -&amp;gt;release()), we have a UAF. dma_buf_fd() is a combination of reserving a descriptor and fd_install(). habanalabs export_dmabuf() calls it and then proceeds to access the objects destroyed on close.  In particular, it grabs an extra reference to another struct file that will be dropped as part of -&amp;gt;release() for ours; that &amp;#34;will be&amp;#34; is actually &amp;#34;might have already been&amp;#34;. Fix that by reserving descriptor before anything else and do fd_install() only when everything had been set up.  As a side benefit, we no longer have the failure exit with file already created, but reference to underlying file (as well as -&amp;gt;dmabuf_export_cnt, etc.) not grabbed yet; unlike dma_buf_fd(), fd_install() can&amp;#39;t fail.&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 124 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: habanalabs: fix UAF in export_dmabuf() As soon as we&amp;#39;d inserted a file reference into descriptor table, another thread could close it.  That&amp;#39;s fine for the case when all we are doing is returning that descriptor to userland (it&amp;#39;s a race, but it&amp;#39;s a userland race and there&amp;#39;s nothing the kernel can do about it).  However, if we follow fd_install() with any kind of access to objects that would be destroyed on close (be it the struct file itself or anything destroyed by its -&amp;gt;release()), we have a UAF. dma_buf_fd() is a combination of reserving a descriptor and fd_install(). habanalabs export_dmabuf() calls it and then proceeds to access the objects destroyed on close.  In particular, it grabs an extra reference to another struct file that will be dropped as part of -&amp;gt;release() for ours; that &amp;#34;will be&amp;#34; is actually &amp;#34;might have already been&amp;#34;. Fix that by reserving descriptor before anything else and do fd_install() only when everything had been set up.  As a side benefit, we no longer have the failure exit with file already created, but reference to underlying file (as well as -&amp;gt;dmabuf_export_cnt, etc.) not grabbed yet; unlike dma_buf_fd(), fd_install() can&amp;#39;t fail.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38722</guid>
    </item>
  </channel>
</rss>
