<?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>Sat, 03 Oct 2026 11:35:34 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72119</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-72119</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2026-72119</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1069 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Elles permettent à un attaquant de p…</title>
      <link>https://vulnerability.circl.lu/vuln/certfr-2026-avi-1069</link>
      <description>certfr-2026-avi-1069</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-1069</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72119</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-72119</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: bcm: extend bcm_tx_lock usage for data and timer updates&lt;/p&gt;
&lt;p&gt;Stage new CAN frame content for an existing tx op into a kmalloc()&amp;#39;d
buffer and validate it there, mirroring the approach already used in
bcm_rx_setup(). Only copy the validated data into op-&amp;gt;frames while
holding op-&amp;gt;bcm_tx_lock, so bcm_can_tx() and bcm_tx_timeout_handler()
can no longer observe a partially updated or unvalidated frame.&lt;/p&gt;
&lt;p&gt;Add a missing error path for memcpy_from_msg() when copying CAN frame
data from userspace.&lt;/p&gt;
&lt;p&gt;Also move the kt_ival1/kt_ival2/ival1/ival2 updates in bcm_tx_setup()
under op-&amp;gt;bcm_tx_lock, and read kt_ival1/kt_ival2/count under the same
lock in bcm_tx_set_expiry() and bcm_tx_timeout_handler(), closing the
torn 64-bit ktime_t read on 32-bit platforms.&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;can: bcm: extend bcm_tx_lock usage for data and timer updates&lt;/p&gt;
&lt;p&gt;Stage new CAN frame content for an existing tx op into a kmalloc()&amp;#39;d
buffer and validate it there, mirroring the approach already used in
bcm_rx_setup(). Only copy the validated data into op-&amp;gt;frames while
holding op-&amp;gt;bcm_tx_lock, so bcm_can_tx() and bcm_tx_timeout_handler()
can no longer observe a partially updated or unvalidated frame.&lt;/p&gt;
&lt;p&gt;Add a missing error path for memcpy_from_msg() when copying CAN frame
data from userspace.&lt;/p&gt;
&lt;p&gt;Also move the kt_ival1/kt_ival2/ival1/ival2 updates in bcm_tx_setup()
under op-&amp;gt;bcm_tx_lock, and read kt_ival1/kt_ival2/count under the same
lock in bcm_tx_set_expiry() and bcm_tx_timeout_handler(), closing the
torn 64-bit ktime_t read on 32-bit platforms.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-72119</guid>
    </item>
    <item>
      <title>GHSA-8pfg-cf9x-g4pr</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-8pfg-cf9x-g4pr</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;can: bcm: extend bcm_tx_lock usage for data and timer updates&lt;/p&gt;
&lt;p&gt;Stage new CAN frame content for an existing tx op into a kmalloc()&amp;#39;d
buffer and validate it there, mirroring the approach already used in
bcm_rx_setup(). Only copy the validated data into op-&amp;gt;frames while
holding op-&amp;gt;bcm_tx_lock, so bcm_can_tx() and bcm_tx_timeout_handler()
can no longer observe a partially updated or unvalidated frame.&lt;/p&gt;
&lt;p&gt;Add a missing error path for memcpy_from_msg() when copying CAN frame
data from userspace.&lt;/p&gt;
&lt;p&gt;Also move the kt_ival1/kt_ival2/ival1/ival2 updates in bcm_tx_setup()
under op-&amp;gt;bcm_tx_lock, and read kt_ival1/kt_ival2/count under the same
lock in bcm_tx_set_expiry() and bcm_tx_timeout_handler(), closing the
torn 64-bit ktime_t read on 32-bit platforms.&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;can: bcm: extend bcm_tx_lock usage for data and timer updates&lt;/p&gt;
&lt;p&gt;Stage new CAN frame content for an existing tx op into a kmalloc()&amp;#39;d
buffer and validate it there, mirroring the approach already used in
bcm_rx_setup(). Only copy the validated data into op-&amp;gt;frames while
holding op-&amp;gt;bcm_tx_lock, so bcm_can_tx() and bcm_tx_timeout_handler()
can no longer observe a partially updated or unvalidated frame.&lt;/p&gt;
&lt;p&gt;Add a missing error path for memcpy_from_msg() when copying CAN frame
data from userspace.&lt;/p&gt;
&lt;p&gt;Also move the kt_ival1/kt_ival2/ival1/ival2 updates in bcm_tx_setup()
under op-&amp;gt;bcm_tx_lock, and read kt_ival1/kt_ival2/count under the same
lock in bcm_tx_set_expiry() and bcm_tx_timeout_handler(), closing the
torn 64-bit ktime_t read on 32-bit platforms.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-8pfg-cf9x-g4pr</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72119</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-72119</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 189 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: bcm: extend bcm_tx_lock usage for data and timer updates Stage new CAN frame content for an existing tx op into a kmalloc()&amp;#39;d buffer and validate it there, mirroring the approach already used in bcm_rx_setup(). Only copy the validated data into op-&amp;gt;frames while holding op-&amp;gt;bcm_tx_lock, so bcm_can_tx() and bcm_tx_timeout_handler() can no longer observe a partially updated or unvalidated frame. Add a missing error path for memcpy_from_msg() when copying CAN frame data from userspace. Also move the kt_ival1/kt_ival2/ival1/ival2 updates in bcm_tx_setup() under op-&amp;gt;bcm_tx_lock, and read kt_ival1/kt_ival2/count under the same lock in bcm_tx_set_expiry() and bcm_tx_timeout_handler(), closing the torn 64-bit ktime_t read on 32-bit platforms.&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 189 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: can: bcm: extend bcm_tx_lock usage for data and timer updates Stage new CAN frame content for an existing tx op into a kmalloc()&amp;#39;d buffer and validate it there, mirroring the approach already used in bcm_rx_setup(). Only copy the validated data into op-&amp;gt;frames while holding op-&amp;gt;bcm_tx_lock, so bcm_can_tx() and bcm_tx_timeout_handler() can no longer observe a partially updated or unvalidated frame. Add a missing error path for memcpy_from_msg() when copying CAN frame data from userspace. Also move the kt_ival1/kt_ival2/ival1/ival2 updates in bcm_tx_setup() under op-&amp;gt;bcm_tx_lock, and read kt_ival1/kt_ival2/count under the same lock in bcm_tx_set_expiry() and bcm_tx_timeout_handler(), closing the torn 64-bit ktime_t read on 32-bit platforms.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-72119</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
