<?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 18:21:04 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98053</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-98053</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ASoC: Intel: avs: Refactor and fix init_config access&lt;/p&gt;
&lt;p&gt;Existing code accesses enties found in -&amp;gt;init_configs array through
indexes that are part of -&amp;gt;config_ids array.  Those two are limited by:
-&amp;gt;num_init_configs and -&amp;gt;num_config_ids respectively.  Using ID larger
or equal to -&amp;gt;num_init_configs leads to out-of-bounds access:&lt;/p&gt;
&lt;p&gt;avs_path_module_send_init_configs()
loop:
	(...) &amp;amp;acomp-&amp;gt;tplg-&amp;gt;init_configs[ids[i]]
					^ out-of-bounds candidate&lt;/p&gt;
&lt;p&gt;Rather than adding another if-statement, refactor the code.  There is no
need to store the IDs, have a list of pointers to actual config-entries
instead.  As the verification of -&amp;gt;init_config entries does not differ from
verification of other types that are part of the topology.c file, simply
reuse the code.&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;ASoC: Intel: avs: Refactor and fix init_config access&lt;/p&gt;
&lt;p&gt;Existing code accesses enties found in -&amp;gt;init_configs array through
indexes that are part of -&amp;gt;config_ids array.  Those two are limited by:
-&amp;gt;num_init_configs and -&amp;gt;num_config_ids respectively.  Using ID larger
or equal to -&amp;gt;num_init_configs leads to out-of-bounds access:&lt;/p&gt;
&lt;p&gt;avs_path_module_send_init_configs()
loop:
	(...) &amp;amp;acomp-&amp;gt;tplg-&amp;gt;init_configs[ids[i]]
					^ out-of-bounds candidate&lt;/p&gt;
&lt;p&gt;Rather than adding another if-statement, refactor the code.  There is no
need to store the IDs, have a list of pointers to actual config-entries
instead.  As the verification of -&amp;gt;init_config entries does not differ from
verification of other types that are part of the topology.c file, simply
reuse the code.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-98053</guid>
    </item>
    <item>
      <title>GHSA-xpmc-f98f-h67j</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-xpmc-f98f-h67j</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ASoC: Intel: avs: Refactor and fix init_config access&lt;/p&gt;
&lt;p&gt;Existing code accesses enties found in -&amp;gt;init_configs array through
indexes that are part of -&amp;gt;config_ids array.  Those two are limited by:
-&amp;gt;num_init_configs and -&amp;gt;num_config_ids respectively.  Using ID larger
or equal to -&amp;gt;num_init_configs leads to out-of-bounds access:&lt;/p&gt;
&lt;p&gt;avs_path_module_send_init_configs()
loop:
	(...) &amp;amp;acomp-&amp;gt;tplg-&amp;gt;init_configs[ids[i]]
					^ out-of-bounds candidate&lt;/p&gt;
&lt;p&gt;Rather than adding another if-statement, refactor the code.  There is no
need to store the IDs, have a list of pointers to actual config-entries
instead.  As the verification of -&amp;gt;init_config entries does not differ from
verification of other types that are part of the topology.c file, simply
reuse the code.&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;ASoC: Intel: avs: Refactor and fix init_config access&lt;/p&gt;
&lt;p&gt;Existing code accesses enties found in -&amp;gt;init_configs array through
indexes that are part of -&amp;gt;config_ids array.  Those two are limited by:
-&amp;gt;num_init_configs and -&amp;gt;num_config_ids respectively.  Using ID larger
or equal to -&amp;gt;num_init_configs leads to out-of-bounds access:&lt;/p&gt;
&lt;p&gt;avs_path_module_send_init_configs()
loop:
	(...) &amp;amp;acomp-&amp;gt;tplg-&amp;gt;init_configs[ids[i]]
					^ out-of-bounds candidate&lt;/p&gt;
&lt;p&gt;Rather than adding another if-statement, refactor the code.  There is no
need to store the IDs, have a list of pointers to actual config-entries
instead.  As the verification of -&amp;gt;init_config entries does not differ from
verification of other types that are part of the topology.c file, simply
reuse the code.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-xpmc-f98f-h67j</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98053</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98053</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: ASoC: Intel: avs: Refactor and fix init_config access Existing code accesses enties found in -&amp;gt;init_configs array through indexes that are part of -&amp;gt;config_ids array.  Those two are limited by: -&amp;gt;num_init_configs and -&amp;gt;num_config_ids respectively.  Using ID larger or equal to -&amp;gt;num_init_configs leads to out-of-bounds access: avs_path_module_send_init_configs() loop: 	(...) &amp;amp;acomp-&amp;gt;tplg-&amp;gt;init_configs[ids[i]] 					^ out-of-bounds candidate Rather than adding another if-statement, refactor the code.  There is no need to store the IDs, have a list of pointers to actual config-entries instead.  As the verification of -&amp;gt;init_config entries does not differ from verification of other types that are part of the topology.c file, simply reuse the code.&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: ASoC: Intel: avs: Refactor and fix init_config access Existing code accesses enties found in -&amp;gt;init_configs array through indexes that are part of -&amp;gt;config_ids array.  Those two are limited by: -&amp;gt;num_init_configs and -&amp;gt;num_config_ids respectively.  Using ID larger or equal to -&amp;gt;num_init_configs leads to out-of-bounds access: avs_path_module_send_init_configs() loop: 	(...) &amp;amp;acomp-&amp;gt;tplg-&amp;gt;init_configs[ids[i]] 					^ out-of-bounds candidate Rather than adding another if-statement, refactor the code.  There is no need to store the IDs, have a list of pointers to actual config-entries instead.  As the verification of -&amp;gt;init_config entries does not differ from verification of other types that are part of the topology.c file, simply reuse the code.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98053</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>
