<?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 12:27:50 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72409</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-72409</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://127.0.0.1:10001/vuln/bell-cve-2026-72409</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1286 — 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-1286</link>
      <description>certfr-2026-avi-1286</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1286</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72409</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-72409</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: mvneta: re-enable percpu interrupt on resume On Marvell MPIC platforms (Armada 370/XP/38x), mvneta uses a percpu IRQ disable/enable scheme for NAPI: the ISR (mvneta_percpu_isr) calls disable_percpu_irq() to mask the MPIC per-CPU interrupt and schedules NAPI poll, which calls enable_percpu_irq() on completion to unmask. If suspend occurs while NAPI poll is pending (between disable_percpu_irq in the ISR and enable_percpu_irq in poll completion), the interrupt is never re-enabled:   1. mvneta_percpu_isr: disable_percpu_irq() + napi_schedule()      =&amp;gt; MPIC masked, percpu_enabled cpumask bit cleared   2. NAPI poll does not complete before suspend proceeds      (on PREEMPT_RT this is highly likely since softirqs run in      ksoftirqd which gets frozen; on non-RT it can happen when      softirq processing is deferred to ksoftirqd)   3. mvneta_stop_dev =&amp;gt; napi_disable(): cancels the pending poll      without executing the completion path   4. suspend_device_irqs =&amp;gt; IRQCHIP_MASK_ON_SUSPEND: masks MPIC      (already masked, but records IRQS_SUSPENDED)   5. Resume: mpic_resume checks irq_percpu_is_enabled() =&amp;gt; false      (bit was cleared in step 1) =&amp;gt; skips unmask   6. mvneta_start_dev only restores device-level INTR_NEW_MASK,      does not touch the MPIC per-CPU mask Result: MPIC per-CPU interrupt stays masked permanently. The NIC generates interrupts (INTR_NEW_CAUSE != 0) but the CPU never receives them, causing…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 247 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net: mvneta: re-enable percpu interrupt on resume On Marvell MPIC platforms (Armada 370/XP/38x), mvneta uses a percpu IRQ disable/enable scheme for NAPI: the ISR (mvneta_percpu_isr) calls disable_percpu_irq() to mask the MPIC per-CPU interrupt and schedules NAPI poll, which calls enable_percpu_irq() on completion to unmask. If suspend occurs while NAPI poll is pending (between disable_percpu_irq in the ISR and enable_percpu_irq in poll completion), the interrupt is never re-enabled:   1. mvneta_percpu_isr: disable_percpu_irq() + napi_schedule()      =&amp;gt; MPIC masked, percpu_enabled cpumask bit cleared   2. NAPI poll does not complete before suspend proceeds      (on PREEMPT_RT this is highly likely since softirqs run in      ksoftirqd which gets frozen; on non-RT it can happen when      softirq processing is deferred to ksoftirqd)   3. mvneta_stop_dev =&amp;gt; napi_disable(): cancels the pending poll      without executing the completion path   4. suspend_device_irqs =&amp;gt; IRQCHIP_MASK_ON_SUSPEND: masks MPIC      (already masked, but records IRQS_SUSPENDED)   5. Resume: mpic_resume checks irq_percpu_is_enabled() =&amp;gt; false      (bit was cleared in step 1) =&amp;gt; skips unmask   6. mvneta_start_dev only restores device-level INTR_NEW_MASK,      does not touch the MPIC per-CPU mask Result: MPIC per-CPU interrupt stays masked permanently. The NIC generates interrupts (INTR_NEW_CAUSE != 0) but the CPU never receives them, causing…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-72409</guid>
    </item>
  </channel>
</rss>
