<?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:08 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-98077</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-98077</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nf_conntrack_sip: fix OOB read in sip_skip_whitespace()&lt;/p&gt;
&lt;p&gt;sip_skip_whitespace() returns dptr unchanged when its own loop
exhausts the buffer (dptr == limit), instead of NULL like its sibling
sip_follow_continuation() returns on its own &amp;#34;no more data&amp;#34; path.&lt;/p&gt;
&lt;p&gt;ct_sip_get_header() only checks for NULL after calling it:&lt;/p&gt;
&lt;p&gt;dptr = sip_skip_whitespace(dptr, limit);
  if (dptr == NULL)
          break;
  if (*dptr != &amp;#39;:&amp;#39; || ++dptr &amp;gt;= limit)
          break;&lt;/p&gt;
&lt;p&gt;so a recognized header name followed only by spaces/tabs running to
the exact end of the SIP payload, with no colon, makes the very next
statement read one byte past the buffer.&lt;/p&gt;
&lt;p&gt;Make both &amp;#34;no more data&amp;#34; outcomes return NULL, matching the
convention sip_follow_continuation() already uses and that both
existing callers already check for.&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;netfilter: nf_conntrack_sip: fix OOB read in sip_skip_whitespace()&lt;/p&gt;
&lt;p&gt;sip_skip_whitespace() returns dptr unchanged when its own loop
exhausts the buffer (dptr == limit), instead of NULL like its sibling
sip_follow_continuation() returns on its own &amp;#34;no more data&amp;#34; path.&lt;/p&gt;
&lt;p&gt;ct_sip_get_header() only checks for NULL after calling it:&lt;/p&gt;
&lt;p&gt;dptr = sip_skip_whitespace(dptr, limit);
  if (dptr == NULL)
          break;
  if (*dptr != &amp;#39;:&amp;#39; || ++dptr &amp;gt;= limit)
          break;&lt;/p&gt;
&lt;p&gt;so a recognized header name followed only by spaces/tabs running to
the exact end of the SIP payload, with no colon, makes the very next
statement read one byte past the buffer.&lt;/p&gt;
&lt;p&gt;Make both &amp;#34;no more data&amp;#34; outcomes return NULL, matching the
convention sip_follow_continuation() already uses and that both
existing callers already check for.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-98077</guid>
    </item>
    <item>
      <title>GHSA-x62x-qq6c-v89q</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-x62x-qq6c-v89q</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nf_conntrack_sip: fix OOB read in sip_skip_whitespace()&lt;/p&gt;
&lt;p&gt;sip_skip_whitespace() returns dptr unchanged when its own loop
exhausts the buffer (dptr == limit), instead of NULL like its sibling
sip_follow_continuation() returns on its own &amp;#34;no more data&amp;#34; path.&lt;/p&gt;
&lt;p&gt;ct_sip_get_header() only checks for NULL after calling it:&lt;/p&gt;
&lt;p&gt;dptr = sip_skip_whitespace(dptr, limit);
  if (dptr == NULL)
          break;
  if (*dptr != &amp;#39;:&amp;#39; || ++dptr &amp;gt;= limit)
          break;&lt;/p&gt;
&lt;p&gt;so a recognized header name followed only by spaces/tabs running to
the exact end of the SIP payload, with no colon, makes the very next
statement read one byte past the buffer.&lt;/p&gt;
&lt;p&gt;Make both &amp;#34;no more data&amp;#34; outcomes return NULL, matching the
convention sip_follow_continuation() already uses and that both
existing callers already check for.&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;netfilter: nf_conntrack_sip: fix OOB read in sip_skip_whitespace()&lt;/p&gt;
&lt;p&gt;sip_skip_whitespace() returns dptr unchanged when its own loop
exhausts the buffer (dptr == limit), instead of NULL like its sibling
sip_follow_continuation() returns on its own &amp;#34;no more data&amp;#34; path.&lt;/p&gt;
&lt;p&gt;ct_sip_get_header() only checks for NULL after calling it:&lt;/p&gt;
&lt;p&gt;dptr = sip_skip_whitespace(dptr, limit);
  if (dptr == NULL)
          break;
  if (*dptr != &amp;#39;:&amp;#39; || ++dptr &amp;gt;= limit)
          break;&lt;/p&gt;
&lt;p&gt;so a recognized header name followed only by spaces/tabs running to
the exact end of the SIP payload, with no colon, makes the very next
statement read one byte past the buffer.&lt;/p&gt;
&lt;p&gt;Make both &amp;#34;no more data&amp;#34; outcomes return NULL, matching the
convention sip_follow_continuation() already uses and that both
existing callers already check for.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-x62x-qq6c-v89q</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98077</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98077</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: netfilter: nf_conntrack_sip: fix OOB read in sip_skip_whitespace() sip_skip_whitespace() returns dptr unchanged when its own loop exhausts the buffer (dptr == limit), instead of NULL like its sibling sip_follow_continuation() returns on its own &amp;#34;no more data&amp;#34; path. ct_sip_get_header() only checks for NULL after calling it:   dptr = sip_skip_whitespace(dptr, limit);   if (dptr == NULL)           break;   if (*dptr != &amp;#39;:&amp;#39; || ++dptr &amp;gt;= limit)           break; so a recognized header name followed only by spaces/tabs running to the exact end of the SIP payload, with no colon, makes the very next statement read one byte past the buffer. Make both &amp;#34;no more data&amp;#34; outcomes return NULL, matching the convention sip_follow_continuation() already uses and that both existing callers already check for.&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: netfilter: nf_conntrack_sip: fix OOB read in sip_skip_whitespace() sip_skip_whitespace() returns dptr unchanged when its own loop exhausts the buffer (dptr == limit), instead of NULL like its sibling sip_follow_continuation() returns on its own &amp;#34;no more data&amp;#34; path. ct_sip_get_header() only checks for NULL after calling it:   dptr = sip_skip_whitespace(dptr, limit);   if (dptr == NULL)           break;   if (*dptr != &amp;#39;:&amp;#39; || ++dptr &amp;gt;= limit)           break; so a recognized header name followed only by spaces/tabs running to the exact end of the SIP payload, with no colon, makes the very next statement read one byte past the buffer. Make both &amp;#34;no more data&amp;#34; outcomes return NULL, matching the convention sip_follow_continuation() already uses and that both existing callers already check for.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-98077</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>
