<?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>Fri, 23 Oct 2026 11:01:06 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-00809</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-00809</link>
      <description>bdu:2025-00809</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-00809</guid>
    </item>
    <item>
      <title>EUVD-2026-309487</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309487</link>
      <description>EUVD-2026-309487</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309487</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47010</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47010</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: Only allow init netns to set default tcp cong to a restricted algo&lt;/p&gt;
&lt;p&gt;tcp_set_default_congestion_control() is netns-safe in that it writes
to &amp;amp;net-&amp;gt;ipv4.tcp_congestion_control, but it also sets
ca-&amp;gt;flags |= TCP_CONG_NON_RESTRICTED which is not namespaced.
This has the unintended side-effect of changing the global
net.ipv4.tcp_allowed_congestion_control sysctl, despite the fact that it
is read-only: 97684f0970f6 (&amp;#34;net: Make tcp_allowed_congestion_control
readonly in non-init netns&amp;#34;)&lt;/p&gt;
&lt;p&gt;Resolve this netns &amp;#34;leak&amp;#34; by only allowing the init netns to set the
default algorithm to one that is restricted. This restriction could be
removed if tcp_allowed_congestion_control were namespace-ified in the
future.&lt;/p&gt;
&lt;p&gt;This bug was uncovered with
https://github.com/JonathonReinhart/linux-netns-sysctl-verify&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: Only allow init netns to set default tcp cong to a restricted algo&lt;/p&gt;
&lt;p&gt;tcp_set_default_congestion_control() is netns-safe in that it writes
to &amp;amp;net-&amp;gt;ipv4.tcp_congestion_control, but it also sets
ca-&amp;gt;flags |= TCP_CONG_NON_RESTRICTED which is not namespaced.
This has the unintended side-effect of changing the global
net.ipv4.tcp_allowed_congestion_control sysctl, despite the fact that it
is read-only: 97684f0970f6 (&amp;#34;net: Make tcp_allowed_congestion_control
readonly in non-init netns&amp;#34;)&lt;/p&gt;
&lt;p&gt;Resolve this netns &amp;#34;leak&amp;#34; by only allowing the init netns to set the
default algorithm to one that is restricted. This restriction could be
removed if tcp_allowed_congestion_control were namespace-ified in the
future.&lt;/p&gt;
&lt;p&gt;This bug was uncovered with
https://github.com/JonathonReinhart/linux-netns-sysctl-verify&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47010</guid>
    </item>
    <item>
      <title>GHSA-c8v5-2jcx-x4j2</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c8v5-2jcx-x4j2</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: Only allow init netns to set default tcp cong to a restricted algo&lt;/p&gt;
&lt;p&gt;tcp_set_default_congestion_control() is netns-safe in that it writes
to &amp;amp;net-&amp;gt;ipv4.tcp_congestion_control, but it also sets
ca-&amp;gt;flags |= TCP_CONG_NON_RESTRICTED which is not namespaced.
This has the unintended side-effect of changing the global
net.ipv4.tcp_allowed_congestion_control sysctl, despite the fact that it
is read-only: 97684f0970f6 (&amp;#34;net: Make tcp_allowed_congestion_control
readonly in non-init netns&amp;#34;)&lt;/p&gt;
&lt;p&gt;Resolve this netns &amp;#34;leak&amp;#34; by only allowing the init netns to set the
default algorithm to one that is restricted. This restriction could be
removed if tcp_allowed_congestion_control were namespace-ified in the
future.&lt;/p&gt;
&lt;p&gt;This bug was uncovered with
https://github.com/JonathonReinhart/linux-netns-sysctl-verify&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: Only allow init netns to set default tcp cong to a restricted algo&lt;/p&gt;
&lt;p&gt;tcp_set_default_congestion_control() is netns-safe in that it writes
to &amp;amp;net-&amp;gt;ipv4.tcp_congestion_control, but it also sets
ca-&amp;gt;flags |= TCP_CONG_NON_RESTRICTED which is not namespaced.
This has the unintended side-effect of changing the global
net.ipv4.tcp_allowed_congestion_control sysctl, despite the fact that it
is read-only: 97684f0970f6 (&amp;#34;net: Make tcp_allowed_congestion_control
readonly in non-init netns&amp;#34;)&lt;/p&gt;
&lt;p&gt;Resolve this netns &amp;#34;leak&amp;#34; by only allowing the init netns to set the
default algorithm to one that is restricted. This restriction could be
removed if tcp_allowed_congestion_control were namespace-ified in the
future.&lt;/p&gt;
&lt;p&gt;This bug was uncovered with
https://github.com/JonathonReinhart/linux-netns-sysctl-verify&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c8v5-2jcx-x4j2</guid>
    </item>
    <item>
      <title>gsd-2021-47010</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-47010</link>
      <description>gsd-2021-47010</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-47010</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47010</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47010</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 100 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: Only allow init netns to set default tcp cong to a restricted algo tcp_set_default_congestion_control() is netns-safe in that it writes to &amp;amp;net-&amp;gt;ipv4.tcp_congestion_control, but it also sets ca-&amp;gt;flags |= TCP_CONG_NON_RESTRICTED which is not namespaced. This has the unintended side-effect of changing the global net.ipv4.tcp_allowed_congestion_control sysctl, despite the fact that it is read-only: 97684f0970f6 (&amp;#34;net: Make tcp_allowed_congestion_control readonly in non-init netns&amp;#34;) Resolve this netns &amp;#34;leak&amp;#34; by only allowing the init netns to set the default algorithm to one that is restricted. This restriction could be removed if tcp_allowed_congestion_control were namespace-ified in the future. This bug was uncovered with https://github.com/JonathonReinhart/linux-netns-sysctl-verify&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux, Ubuntu:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.4 and 100 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: Only allow init netns to set default tcp cong to a restricted algo tcp_set_default_congestion_control() is netns-safe in that it writes to &amp;amp;net-&amp;gt;ipv4.tcp_congestion_control, but it also sets ca-&amp;gt;flags |= TCP_CONG_NON_RESTRICTED which is not namespaced. This has the unintended side-effect of changing the global net.ipv4.tcp_allowed_congestion_control sysctl, despite the fact that it is read-only: 97684f0970f6 (&amp;#34;net: Make tcp_allowed_congestion_control readonly in non-init netns&amp;#34;) Resolve this netns &amp;#34;leak&amp;#34; by only allowing the init netns to set the default algorithm to one that is restricted. This restriction could be removed if tcp_allowed_congestion_control were namespace-ified in the future. This bug was uncovered with https://github.com/JonathonReinhart/linux-netns-sysctl-verify&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47010</guid>
    </item>
  </channel>
</rss>
