<?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 10:57:38 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-68202</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-68202</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-2025-68202</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0128 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0128</link>
      <description>certfr-2026-avi-0128</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0128</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-68202</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-68202</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 103 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched_ext: Fix unsafe locking in the scx_dump_state() For built with CONFIG_PREEMPT_RT=y kernels, the dump_lock will be converted sleepable spinlock and not disable-irq, so the following scenarios occur: inconsistent {IN-HARDIRQ-W} -&amp;gt; {HARDIRQ-ON-W} usage. irq_work/0/27 [HC0[0]:SC0[0]:HE1:SE1] takes: (&amp;amp;rq-&amp;gt;__lock){?...}-{2:2}, at: raw_spin_rq_lock_nested+0x2b/0x40 {IN-HARDIRQ-W} state was registered at:    lock_acquire+0x1e1/0x510    _raw_spin_lock_nested+0x42/0x80    raw_spin_rq_lock_nested+0x2b/0x40    sched_tick+0xae/0x7b0    update_process_times+0x14c/0x1b0    tick_periodic+0x62/0x1f0    tick_handle_periodic+0x48/0xf0    timer_interrupt+0x55/0x80    __handle_irq_event_percpu+0x20a/0x5c0    handle_irq_event_percpu+0x18/0xc0    handle_irq_event+0xb5/0x150    handle_level_irq+0x220/0x460    __common_interrupt+0xa2/0x1e0    common_interrupt+0xb0/0xd0    asm_common_interrupt+0x2b/0x40    _raw_spin_unlock_irqrestore+0x45/0x80    __setup_irq+0xc34/0x1a30    request_threaded_irq+0x214/0x2f0    hpet_time_init+0x3e/0x60    x86_late_time_init+0x5b/0xb0    start_kernel+0x308/0x410    x86_64_start_reservations+0x1c/0x30    x86_64_start_kernel+0x96/0xa0    common_startup_64+0x13e/0x148  other info that might help us debug this:  Possible unsafe locking scenario:         CPU0         ----    lock(&amp;amp;rq-&amp;gt;__lock);    &amp;lt;Interrupt&amp;gt;      lock(&amp;amp;rq-&amp;gt;__lock);   *** DEADLOCK ***  stack backtrace:  CPU: 0 UID: 0 PID: 27 Comm: irq_w…&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 103 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sched_ext: Fix unsafe locking in the scx_dump_state() For built with CONFIG_PREEMPT_RT=y kernels, the dump_lock will be converted sleepable spinlock and not disable-irq, so the following scenarios occur: inconsistent {IN-HARDIRQ-W} -&amp;gt; {HARDIRQ-ON-W} usage. irq_work/0/27 [HC0[0]:SC0[0]:HE1:SE1] takes: (&amp;amp;rq-&amp;gt;__lock){?...}-{2:2}, at: raw_spin_rq_lock_nested+0x2b/0x40 {IN-HARDIRQ-W} state was registered at:    lock_acquire+0x1e1/0x510    _raw_spin_lock_nested+0x42/0x80    raw_spin_rq_lock_nested+0x2b/0x40    sched_tick+0xae/0x7b0    update_process_times+0x14c/0x1b0    tick_periodic+0x62/0x1f0    tick_handle_periodic+0x48/0xf0    timer_interrupt+0x55/0x80    __handle_irq_event_percpu+0x20a/0x5c0    handle_irq_event_percpu+0x18/0xc0    handle_irq_event+0xb5/0x150    handle_level_irq+0x220/0x460    __common_interrupt+0xa2/0x1e0    common_interrupt+0xb0/0xd0    asm_common_interrupt+0x2b/0x40    _raw_spin_unlock_irqrestore+0x45/0x80    __setup_irq+0xc34/0x1a30    request_threaded_irq+0x214/0x2f0    hpet_time_init+0x3e/0x60    x86_late_time_init+0x5b/0xb0    start_kernel+0x308/0x410    x86_64_start_reservations+0x1c/0x30    x86_64_start_kernel+0x96/0xa0    common_startup_64+0x13e/0x148  other info that might help us debug this:  Possible unsafe locking scenario:         CPU0         ----    lock(&amp;amp;rq-&amp;gt;__lock);    &amp;lt;Interrupt&amp;gt;      lock(&amp;amp;rq-&amp;gt;__lock);   *** DEADLOCK ***  stack backtrace:  CPU: 0 UID: 0 PID: 27 Comm: irq_w…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-68202</guid>
    </item>
  </channel>
</rss>
