<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T16:11:06.228704+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2026-80727</id>
    <title>BELL-CVE-2026-80727</title>
    <updated>2026-11-21T16:11:06.233594+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2026-80727"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-1232</id>
    <title>certfr-2026-avi-1232 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
    <updated>2026-11-21T16:11:06.233622+00:00</updated>
    <content>certfr-2026-avi-1232</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-1232"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80727</id>
    <title>UBUNTU-CVE-2026-80727</title>
    <updated>2026-11-21T16:11:06.233633+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 155 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: x86/mce: Set up the polling timer before CMCI discovery I hit the following on one of my machines:   mce: CPU0 BANK15 CMCI inherited storm   ------------[ cut here ]------------   ODEBUG: assert_init not available (active state 0) object: (____ptrval____) object type: timer_list hint: 0x0   WARNING: lib/debugobjects.c:632 at debug_object_assert_init+0x178/0x230, CPU#0: swapper/0/0   CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 7.2.0-rc5 #3 PREEMPTLAZY   RIP: 0010:debug_object_assert_init+0x18f/0x230   Call Trace:    &lt;TASK&gt;    __mod_timer    mce_timer_kick    cmci_discover    intel_init_cmci    mce_intel_feature_init    mcheck_cpu_init    identify_cpu    identify_boot_cpu    arch_cpu_finalize_init    start_kernel A second splat follows right after, from timer_setup() finding that same timer already queued:   ODEBUG: init active (active state 0) object: (____ptrval____) object type: timer_list hint: stub_timer+0x0/0x10 This is happening because CMCI storm detection is trying to modify the timer before latter was properly set up. Set up the timer first. __mcheck_cpu_setup_timer() only calls timer_setup(), and depends on neither the generic nor the vendor init.   [ bp: Massage commit message. ]</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-80727"/>
  </entry>
</feed>
