<?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 11:20:36 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-63874</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-63874</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://127.0.0.1:10001/vuln/bell-cve-2026-63874</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1162 — 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-1162</link>
      <description>certfr-2026-avi-1162</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1162</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-63874</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-63874</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 119 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: mctp: usb: fix race between urb completion and rx_retry cancellation It&amp;#39;s possible that sequencing between setting -&amp;gt;stopped and cancelling the rx_retry work (in ndo_stop) could leave us with an urb queued:     T1: ndo_stop                  T2: rx_retry_work     ------------                  ----------------                                   LD: -&amp;gt;stopped =&amp;gt; false     ST: -&amp;gt;stopped &amp;lt;= true     usb_kill_urb()                                   mctp_usb_rx_queue()                                     usb_submit_urb()     cancel_delayed_work_sync() That urb completion can then re-schedule rx_retry_work. Strenghen the sequencing between the stop (preventing another requeue) and the cancel by updating both atomically under a new rx lock. After setting -&amp;gt;rx_stopped, and cancelling pending work, we know that the requeue cannot occur, so all that&amp;#39;s left is killing any pending urb.&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 119 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: mctp: usb: fix race between urb completion and rx_retry cancellation It&amp;#39;s possible that sequencing between setting -&amp;gt;stopped and cancelling the rx_retry work (in ndo_stop) could leave us with an urb queued:     T1: ndo_stop                  T2: rx_retry_work     ------------                  ----------------                                   LD: -&amp;gt;stopped =&amp;gt; false     ST: -&amp;gt;stopped &amp;lt;= true     usb_kill_urb()                                   mctp_usb_rx_queue()                                     usb_submit_urb()     cancel_delayed_work_sync() That urb completion can then re-schedule rx_retry_work. Strenghen the sequencing between the stop (preventing another requeue) and the cancel by updating both atomically under a new rx lock. After setting -&amp;gt;rx_stopped, and cancelling pending work, we know that the requeue cannot occur, so all that&amp;#39;s left is killing any pending urb.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-63874</guid>
    </item>
  </channel>
</rss>
