<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 13:20:35 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-43199</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-43199</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-43199</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0831 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0831</link>
      <description>certfr-2026-avi-0831</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0831</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-43199</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43199</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 140 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix &amp;#34;scheduling while atomic&amp;#34; in IPsec MAC address query Fix a &amp;#34;scheduling while atomic&amp;#34; bug in mlx5e_ipsec_init_macs() by replacing mlx5_query_mac_address() with ether_addr_copy() to get the local MAC address directly from netdev-&amp;gt;dev_addr. The issue occurs because mlx5_query_mac_address() queries the hardware which involves mlx5_cmd_exec() that can sleep, but it is called from the mlx5e_ipsec_handle_event workqueue which runs in atomic context. The MAC address is already available in netdev-&amp;gt;dev_addr, so no need to query hardware. This avoids the sleeping call and resolves the bug. Call trace:   BUG: scheduling while atomic: kworker/u112:2/69344/0x00000200   __schedule+0x7ab/0xa20   schedule+0x1c/0xb0   schedule_timeout+0x6e/0xf0   __wait_for_common+0x91/0x1b0   cmd_exec+0xa85/0xff0 [mlx5_core]   mlx5_cmd_exec+0x1f/0x50 [mlx5_core]   mlx5_query_nic_vport_mac_address+0x7b/0xd0 [mlx5_core]   mlx5_query_mac_address+0x19/0x30 [mlx5_core]   mlx5e_ipsec_init_macs+0xc1/0x720 [mlx5_core]   mlx5e_ipsec_build_accel_xfrm_attrs+0x422/0x670 [mlx5_core]   mlx5e_ipsec_handle_event+0x2b9/0x460 [mlx5_core]   process_one_work+0x178/0x2e0   worker_thread+0x2ea/0x430&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 140 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix &amp;#34;scheduling while atomic&amp;#34; in IPsec MAC address query Fix a &amp;#34;scheduling while atomic&amp;#34; bug in mlx5e_ipsec_init_macs() by replacing mlx5_query_mac_address() with ether_addr_copy() to get the local MAC address directly from netdev-&amp;gt;dev_addr. The issue occurs because mlx5_query_mac_address() queries the hardware which involves mlx5_cmd_exec() that can sleep, but it is called from the mlx5e_ipsec_handle_event workqueue which runs in atomic context. The MAC address is already available in netdev-&amp;gt;dev_addr, so no need to query hardware. This avoids the sleeping call and resolves the bug. Call trace:   BUG: scheduling while atomic: kworker/u112:2/69344/0x00000200   __schedule+0x7ab/0xa20   schedule+0x1c/0xb0   schedule_timeout+0x6e/0xf0   __wait_for_common+0x91/0x1b0   cmd_exec+0xa85/0xff0 [mlx5_core]   mlx5_cmd_exec+0x1f/0x50 [mlx5_core]   mlx5_query_nic_vport_mac_address+0x7b/0xd0 [mlx5_core]   mlx5_query_mac_address+0x19/0x30 [mlx5_core]   mlx5e_ipsec_init_macs+0xc1/0x720 [mlx5_core]   mlx5e_ipsec_build_accel_xfrm_attrs+0x422/0x670 [mlx5_core]   mlx5e_ipsec_handle_event+0x2b9/0x460 [mlx5_core]   process_one_work+0x178/0x2e0   worker_thread+0x2ea/0x430&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43199</guid>
    </item>
  </channel>
</rss>
