<?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 14:22:33 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-46272</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-46272</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-46272</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1372 — De multiples vulnérabilités ont été découvertes dans les produits SUSE. Certaines d'entre elles permettent à un attaqua…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1372</link>
      <description>certfr-2026-avi-1372</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1372</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-46272</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-46272</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 142 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: coresight: tmc-etr: Fix race condition between sysfs and perf mode When trying to run perf and sysfs mode simultaneously, the WARN_ON() in tmc_etr_enable_hw() is triggered sometimes:  WARNING: CPU: 42 PID: 3911571 at drivers/hwtracing/coresight/coresight-tmc-etr.c:1060 tmc_etr_enable_hw+0xc0/0xd8 [coresight_tmc]  [..snip..]  Call trace:   tmc_etr_enable_hw+0xc0/0xd8 [coresight_tmc] (P)   tmc_enable_etr_sink+0x11c/0x250 [coresight_tmc] (L)   tmc_enable_etr_sink+0x11c/0x250 [coresight_tmc]   coresight_enable_path+0x1c8/0x218 [coresight]   coresight_enable_sysfs+0xa4/0x228 [coresight]   enable_source_store+0x58/0xa8 [coresight]   dev_attr_store+0x20/0x40   sysfs_kf_write+0x4c/0x68   kernfs_fop_write_iter+0x120/0x1b8   vfs_write+0x2c8/0x388   ksys_write+0x74/0x108   __arm64_sys_write+0x24/0x38   el0_svc_common.constprop.0+0x64/0x148   do_el0_svc+0x24/0x38   el0_svc+0x3c/0x130   el0t_64_sync_handler+0xc8/0xd0   el0t_64_sync+0x1ac/0x1b0  ---[ end trace 0000000000000000 ]--- Since the enablement of sysfs mode is separeted into two critical regions, one for sysfs buffer allocation and another for hardware enablement, it&amp;#39;s possible to race with the perf mode. Fix this by double check whether the perf mode&amp;#39;s been used before enabling the hardware in sysfs mode.  mode:    [sysfs mode]                   [perf mode]    tmc_etr_get_sysfs_buffer()      spin_lock(&amp;amp;drvdata-&amp;gt;spinlock)      [sysfs buffer allocation]      spin_…&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 142 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: coresight: tmc-etr: Fix race condition between sysfs and perf mode When trying to run perf and sysfs mode simultaneously, the WARN_ON() in tmc_etr_enable_hw() is triggered sometimes:  WARNING: CPU: 42 PID: 3911571 at drivers/hwtracing/coresight/coresight-tmc-etr.c:1060 tmc_etr_enable_hw+0xc0/0xd8 [coresight_tmc]  [..snip..]  Call trace:   tmc_etr_enable_hw+0xc0/0xd8 [coresight_tmc] (P)   tmc_enable_etr_sink+0x11c/0x250 [coresight_tmc] (L)   tmc_enable_etr_sink+0x11c/0x250 [coresight_tmc]   coresight_enable_path+0x1c8/0x218 [coresight]   coresight_enable_sysfs+0xa4/0x228 [coresight]   enable_source_store+0x58/0xa8 [coresight]   dev_attr_store+0x20/0x40   sysfs_kf_write+0x4c/0x68   kernfs_fop_write_iter+0x120/0x1b8   vfs_write+0x2c8/0x388   ksys_write+0x74/0x108   __arm64_sys_write+0x24/0x38   el0_svc_common.constprop.0+0x64/0x148   do_el0_svc+0x24/0x38   el0_svc+0x3c/0x130   el0t_64_sync_handler+0xc8/0xd0   el0t_64_sync+0x1ac/0x1b0  ---[ end trace 0000000000000000 ]--- Since the enablement of sysfs mode is separeted into two critical regions, one for sysfs buffer allocation and another for hardware enablement, it&amp;#39;s possible to race with the perf mode. Fix this by double check whether the perf mode&amp;#39;s been used before enabling the hardware in sysfs mode.  mode:    [sysfs mode]                   [perf mode]    tmc_etr_get_sysfs_buffer()      spin_lock(&amp;amp;drvdata-&amp;gt;spinlock)      [sysfs buffer allocation]      spin_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-46272</guid>
    </item>
  </channel>
</rss>
