<?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://cve.radiocsirt.org</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>Thu, 08 Oct 2026 18:26:43 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-22983</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-22983</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-22983</guid>
    </item>
    <item>
      <title>EUVD-2026-315272</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-315272</link>
      <description>EUVD-2026-315272</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-315272</guid>
    </item>
    <item>
      <title>fkie_cve-2026-22983</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-22983</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: do not write to msg_get_inq in callee&lt;/p&gt;
&lt;p&gt;NULL pointer dereference fix.&lt;/p&gt;
&lt;p&gt;msg_get_inq is an input field from caller to callee. Don&amp;#39;t set it in
the callee, as the caller may not clear it on struct reuse.&lt;/p&gt;
&lt;p&gt;This is a kernel-internal variant of msghdr only, and the only user
does reinitialize the field. So this is not critical for that reason.
But it is more robust to avoid the write, and slightly simpler code.
And it fixes a bug, see below.&lt;/p&gt;
&lt;p&gt;Callers set msg_get_inq to request the input queue length to be
returned in msg_inq. This is equivalent to but independent from the
SO_INQ request to return that same info as a cmsg (tp-&amp;gt;recvmsg_inq).
To reduce branching in the hot path the second also sets the msg_inq.
That is WAI.&lt;/p&gt;
&lt;p&gt;This is a fix to commit 4d1442979e4a (&amp;#34;af_unix: don&amp;#39;t post cmsg for
SO_INQ unless explicitly asked for&amp;#34;), which fixed the inverse.&lt;/p&gt;
&lt;p&gt;Also avoid NULL pointer dereference in unix_stream_read_generic if
state-&amp;gt;msg is NULL and msg-&amp;gt;msg_get_inq is written. A NULL state-&amp;gt;msg
can happen when splicing as of commit 2b514574f7e8 (&amp;#34;net: af_unix:
implement splice for stream af_unix sockets&amp;#34;).&lt;/p&gt;
&lt;p&gt;Also collapse two branches using a bitwise or.&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;net: do not write to msg_get_inq in callee&lt;/p&gt;
&lt;p&gt;NULL pointer dereference fix.&lt;/p&gt;
&lt;p&gt;msg_get_inq is an input field from caller to callee. Don&amp;#39;t set it in
the callee, as the caller may not clear it on struct reuse.&lt;/p&gt;
&lt;p&gt;This is a kernel-internal variant of msghdr only, and the only user
does reinitialize the field. So this is not critical for that reason.
But it is more robust to avoid the write, and slightly simpler code.
And it fixes a bug, see below.&lt;/p&gt;
&lt;p&gt;Callers set msg_get_inq to request the input queue length to be
returned in msg_inq. This is equivalent to but independent from the
SO_INQ request to return that same info as a cmsg (tp-&amp;gt;recvmsg_inq).
To reduce branching in the hot path the second also sets the msg_inq.
That is WAI.&lt;/p&gt;
&lt;p&gt;This is a fix to commit 4d1442979e4a (&amp;#34;af_unix: don&amp;#39;t post cmsg for
SO_INQ unless explicitly asked for&amp;#34;), which fixed the inverse.&lt;/p&gt;
&lt;p&gt;Also avoid NULL pointer dereference in unix_stream_read_generic if
state-&amp;gt;msg is NULL and msg-&amp;gt;msg_get_inq is written. A NULL state-&amp;gt;msg
can happen when splicing as of commit 2b514574f7e8 (&amp;#34;net: af_unix:
implement splice for stream af_unix sockets&amp;#34;).&lt;/p&gt;
&lt;p&gt;Also collapse two branches using a bitwise or.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-22983</guid>
    </item>
    <item>
      <title>GHSA-3c6v-88wh-34ph</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3c6v-88wh-34ph</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: do not write to msg_get_inq in callee&lt;/p&gt;
&lt;p&gt;NULL pointer dereference fix.&lt;/p&gt;
&lt;p&gt;msg_get_inq is an input field from caller to callee. Don&amp;#39;t set it in
the callee, as the caller may not clear it on struct reuse.&lt;/p&gt;
&lt;p&gt;This is a kernel-internal variant of msghdr only, and the only user
does reinitialize the field. So this is not critical for that reason.
But it is more robust to avoid the write, and slightly simpler code.
And it fixes a bug, see below.&lt;/p&gt;
&lt;p&gt;Callers set msg_get_inq to request the input queue length to be
returned in msg_inq. This is equivalent to but independent from the
SO_INQ request to return that same info as a cmsg (tp-&amp;gt;recvmsg_inq).
To reduce branching in the hot path the second also sets the msg_inq.
That is WAI.&lt;/p&gt;
&lt;p&gt;This is a fix to commit 4d1442979e4a (&amp;#34;af_unix: don&amp;#39;t post cmsg for
SO_INQ unless explicitly asked for&amp;#34;), which fixed the inverse.&lt;/p&gt;
&lt;p&gt;Also avoid NULL pointer dereference in unix_stream_read_generic if
state-&amp;gt;msg is NULL and msg-&amp;gt;msg_get_inq is written. A NULL state-&amp;gt;msg
can happen when splicing as of commit 2b514574f7e8 (&amp;#34;net: af_unix:
implement splice for stream af_unix sockets&amp;#34;).&lt;/p&gt;
&lt;p&gt;Also collapse two branches using a bitwise or.&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;net: do not write to msg_get_inq in callee&lt;/p&gt;
&lt;p&gt;NULL pointer dereference fix.&lt;/p&gt;
&lt;p&gt;msg_get_inq is an input field from caller to callee. Don&amp;#39;t set it in
the callee, as the caller may not clear it on struct reuse.&lt;/p&gt;
&lt;p&gt;This is a kernel-internal variant of msghdr only, and the only user
does reinitialize the field. So this is not critical for that reason.
But it is more robust to avoid the write, and slightly simpler code.
And it fixes a bug, see below.&lt;/p&gt;
&lt;p&gt;Callers set msg_get_inq to request the input queue length to be
returned in msg_inq. This is equivalent to but independent from the
SO_INQ request to return that same info as a cmsg (tp-&amp;gt;recvmsg_inq).
To reduce branching in the hot path the second also sets the msg_inq.
That is WAI.&lt;/p&gt;
&lt;p&gt;This is a fix to commit 4d1442979e4a (&amp;#34;af_unix: don&amp;#39;t post cmsg for
SO_INQ unless explicitly asked for&amp;#34;), which fixed the inverse.&lt;/p&gt;
&lt;p&gt;Also avoid NULL pointer dereference in unix_stream_read_generic if
state-&amp;gt;msg is NULL and msg-&amp;gt;msg_get_inq is written. A NULL state-&amp;gt;msg
can happen when splicing as of commit 2b514574f7e8 (&amp;#34;net: af_unix:
implement splice for stream af_unix sockets&amp;#34;).&lt;/p&gt;
&lt;p&gt;Also collapse two branches using a bitwise or.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3c6v-88wh-34ph</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-22983</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-22983</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 81 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: do not write to msg_get_inq in callee NULL pointer dereference fix. msg_get_inq is an input field from caller to callee. Don&amp;#39;t set it in the callee, as the caller may not clear it on struct reuse. This is a kernel-internal variant of msghdr only, and the only user does reinitialize the field. So this is not critical for that reason. But it is more robust to avoid the write, and slightly simpler code. And it fixes a bug, see below. Callers set msg_get_inq to request the input queue length to be returned in msg_inq. This is equivalent to but independent from the SO_INQ request to return that same info as a cmsg (tp-&amp;gt;recvmsg_inq). To reduce branching in the hot path the second also sets the msg_inq. That is WAI. This is a fix to commit 4d1442979e4a (&amp;#34;af_unix: don&amp;#39;t post cmsg for SO_INQ unless explicitly asked for&amp;#34;), which fixed the inverse. Also avoid NULL pointer dereference in unix_stream_read_generic if state-&amp;gt;msg is NULL and msg-&amp;gt;msg_get_inq is written. A NULL state-&amp;gt;msg can happen when splicing as of commit 2b514574f7e8 (&amp;#34;net: af_unix: implement splice for stream af_unix sockets&amp;#34;). Also collapse two branches using a bitwise or.&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 81 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: do not write to msg_get_inq in callee NULL pointer dereference fix. msg_get_inq is an input field from caller to callee. Don&amp;#39;t set it in the callee, as the caller may not clear it on struct reuse. This is a kernel-internal variant of msghdr only, and the only user does reinitialize the field. So this is not critical for that reason. But it is more robust to avoid the write, and slightly simpler code. And it fixes a bug, see below. Callers set msg_get_inq to request the input queue length to be returned in msg_inq. This is equivalent to but independent from the SO_INQ request to return that same info as a cmsg (tp-&amp;gt;recvmsg_inq). To reduce branching in the hot path the second also sets the msg_inq. That is WAI. This is a fix to commit 4d1442979e4a (&amp;#34;af_unix: don&amp;#39;t post cmsg for SO_INQ unless explicitly asked for&amp;#34;), which fixed the inverse. Also avoid NULL pointer dereference in unix_stream_read_generic if state-&amp;gt;msg is NULL and msg-&amp;gt;msg_get_inq is written. A NULL state-&amp;gt;msg can happen when splicing as of commit 2b514574f7e8 (&amp;#34;net: af_unix: implement splice for stream af_unix sockets&amp;#34;). Also collapse two branches using a bitwise or.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-22983</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0215 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0215</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0215</guid>
    </item>
  </channel>
</rss>
