<?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, 28 Sep 2026 16:06:00 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98002</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-98002</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu/amd: Fix ineffective error check in nested domain allocation&lt;/p&gt;
&lt;p&gt;amd_iommu_pdom_id_alloc() returns an int: a domain ID on success, or the
negative errno from ida_alloc_range() when the ID space is exhausted or
memory is short.  amd_iommu_alloc_domain_nested() stores that return value
in gdom_info-&amp;gt;hdom_id, which is a u32, and only then tests it:&lt;/p&gt;
&lt;p&gt;gdom_info-&amp;gt;hdom_id = amd_iommu_pdom_id_alloc();
	if (gdom_info-&amp;gt;hdom_id &amp;lt;= 0) {&lt;/p&gt;
&lt;p&gt;The assignment discards the sign, so -ENOSPC becomes 0xffffffe4 and the
test never fires.  The nested domain is then set up with a host domain ID
that was never allocated, instead of the allocation failing with -ENOSPC.&lt;/p&gt;
&lt;p&gt;Keep the value in an int, test it there, and store it only once it is
known to be valid, which is what the other amd_iommu_pdom_id_alloc()
callers already do.&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;iommu/amd: Fix ineffective error check in nested domain allocation&lt;/p&gt;
&lt;p&gt;amd_iommu_pdom_id_alloc() returns an int: a domain ID on success, or the
negative errno from ida_alloc_range() when the ID space is exhausted or
memory is short.  amd_iommu_alloc_domain_nested() stores that return value
in gdom_info-&amp;gt;hdom_id, which is a u32, and only then tests it:&lt;/p&gt;
&lt;p&gt;gdom_info-&amp;gt;hdom_id = amd_iommu_pdom_id_alloc();
	if (gdom_info-&amp;gt;hdom_id &amp;lt;= 0) {&lt;/p&gt;
&lt;p&gt;The assignment discards the sign, so -ENOSPC becomes 0xffffffe4 and the
test never fires.  The nested domain is then set up with a host domain ID
that was never allocated, instead of the allocation failing with -ENOSPC.&lt;/p&gt;
&lt;p&gt;Keep the value in an int, test it there, and store it only once it is
known to be valid, which is what the other amd_iommu_pdom_id_alloc()
callers already do.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-98002</guid>
    </item>
    <item>
      <title>GHSA-38jm-2gpc-m9wh</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-38jm-2gpc-m9wh</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iommu/amd: Fix ineffective error check in nested domain allocation&lt;/p&gt;
&lt;p&gt;amd_iommu_pdom_id_alloc() returns an int: a domain ID on success, or the
negative errno from ida_alloc_range() when the ID space is exhausted or
memory is short.  amd_iommu_alloc_domain_nested() stores that return value
in gdom_info-&amp;gt;hdom_id, which is a u32, and only then tests it:&lt;/p&gt;
&lt;p&gt;gdom_info-&amp;gt;hdom_id = amd_iommu_pdom_id_alloc();
	if (gdom_info-&amp;gt;hdom_id &amp;lt;= 0) {&lt;/p&gt;
&lt;p&gt;The assignment discards the sign, so -ENOSPC becomes 0xffffffe4 and the
test never fires.  The nested domain is then set up with a host domain ID
that was never allocated, instead of the allocation failing with -ENOSPC.&lt;/p&gt;
&lt;p&gt;Keep the value in an int, test it there, and store it only once it is
known to be valid, which is what the other amd_iommu_pdom_id_alloc()
callers already do.&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;iommu/amd: Fix ineffective error check in nested domain allocation&lt;/p&gt;
&lt;p&gt;amd_iommu_pdom_id_alloc() returns an int: a domain ID on success, or the
negative errno from ida_alloc_range() when the ID space is exhausted or
memory is short.  amd_iommu_alloc_domain_nested() stores that return value
in gdom_info-&amp;gt;hdom_id, which is a u32, and only then tests it:&lt;/p&gt;
&lt;p&gt;gdom_info-&amp;gt;hdom_id = amd_iommu_pdom_id_alloc();
	if (gdom_info-&amp;gt;hdom_id &amp;lt;= 0) {&lt;/p&gt;
&lt;p&gt;The assignment discards the sign, so -ENOSPC becomes 0xffffffe4 and the
test never fires.  The nested domain is then set up with a host domain ID
that was never allocated, instead of the allocation failing with -ENOSPC.&lt;/p&gt;
&lt;p&gt;Keep the value in an int, test it there, and store it only once it is
known to be valid, which is what the other amd_iommu_pdom_id_alloc()
callers already do.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-38jm-2gpc-m9wh</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98002</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98002</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Fix ineffective error check in nested domain allocation amd_iommu_pdom_id_alloc() returns an int: a domain ID on success, or the negative errno from ida_alloc_range() when the ID space is exhausted or memory is short.  amd_iommu_alloc_domain_nested() stores that return value in gdom_info-&amp;gt;hdom_id, which is a u32, and only then tests it: 	gdom_info-&amp;gt;hdom_id = amd_iommu_pdom_id_alloc(); 	if (gdom_info-&amp;gt;hdom_id &amp;lt;= 0) { The assignment discards the sign, so -ENOSPC becomes 0xffffffe4 and the test never fires.  The nested domain is then set up with a host domain ID that was never allocated, instead of the allocation failing with -ENOSPC. Keep the value in an int, test it there, and store it only once it is known to be valid, which is what the other amd_iommu_pdom_id_alloc() callers already do.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Fix ineffective error check in nested domain allocation amd_iommu_pdom_id_alloc() returns an int: a domain ID on success, or the negative errno from ida_alloc_range() when the ID space is exhausted or memory is short.  amd_iommu_alloc_domain_nested() stores that return value in gdom_info-&amp;gt;hdom_id, which is a u32, and only then tests it: 	gdom_info-&amp;gt;hdom_id = amd_iommu_pdom_id_alloc(); 	if (gdom_info-&amp;gt;hdom_id &amp;lt;= 0) { The assignment discards the sign, so -ENOSPC becomes 0xffffffe4 and the test never fires.  The nested domain is then set up with a host domain ID that was never allocated, instead of the allocation failing with -ENOSPC. Keep the value in an int, test it there, and store it only once it is known to be valid, which is what the other amd_iommu_pdom_id_alloc() callers already do.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98002</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</guid>
    </item>
  </channel>
</rss>
