<?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>Fri, 20 Nov 2026 23:30:49 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-37901</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-37901</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-2025-37901</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0464 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0464</link>
      <description>certfr-2025-avi-0464</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0464</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-37901</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37901</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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: irqchip/qcom-mpm: Prevent crash when trying to handle non-wake GPIOs On Qualcomm chipsets not all GPIOs are wakeup capable. Those GPIOs do not have a corresponding MPM pin and should not be handled inside the MPM driver. The IRQ domain hierarchy is always applied, so it&amp;#39;s required to explicitly disconnect the hierarchy for those. The pinctrl-msm driver marks these with GPIO_NO_WAKE_IRQ. qcom-pdc has a check for this, but irq-qcom-mpm is currently missing the check. This is causing crashes when setting up interrupts for non-wake GPIOs:  root@rb1:~# gpiomon -c gpiochip1 10    irq: IRQ159: trimming hierarchy from :soc@0:interrupt-controller@f200000-1    Unable to handle kernel paging request at virtual address ffff8000a1dc3820    Hardware name: Qualcomm Technologies, Inc. Robotics RB1 (DT)    pc : mpm_set_type+0x80/0xcc    lr : mpm_set_type+0x5c/0xcc    Call trace:     mpm_set_type+0x80/0xcc (P)     qcom_mpm_set_type+0x64/0x158     irq_chip_set_type_parent+0x20/0x38     msm_gpio_irq_set_type+0x50/0x530     __irq_set_trigger+0x60/0x184     __setup_irq+0x304/0x6bc     request_threaded_irq+0xc8/0x19c     edge_detector_setup+0x260/0x364     linereq_create+0x420/0x5a8     gpio_ioctl+0x2d4/0x6c0 Fix this by copying the check for GPIO_NO_WAKE_IRQ from qcom-pdc.c, so that MPM is removed entirely from the hierarchy for non-wake GPIOs.&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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: irqchip/qcom-mpm: Prevent crash when trying to handle non-wake GPIOs On Qualcomm chipsets not all GPIOs are wakeup capable. Those GPIOs do not have a corresponding MPM pin and should not be handled inside the MPM driver. The IRQ domain hierarchy is always applied, so it&amp;#39;s required to explicitly disconnect the hierarchy for those. The pinctrl-msm driver marks these with GPIO_NO_WAKE_IRQ. qcom-pdc has a check for this, but irq-qcom-mpm is currently missing the check. This is causing crashes when setting up interrupts for non-wake GPIOs:  root@rb1:~# gpiomon -c gpiochip1 10    irq: IRQ159: trimming hierarchy from :soc@0:interrupt-controller@f200000-1    Unable to handle kernel paging request at virtual address ffff8000a1dc3820    Hardware name: Qualcomm Technologies, Inc. Robotics RB1 (DT)    pc : mpm_set_type+0x80/0xcc    lr : mpm_set_type+0x5c/0xcc    Call trace:     mpm_set_type+0x80/0xcc (P)     qcom_mpm_set_type+0x64/0x158     irq_chip_set_type_parent+0x20/0x38     msm_gpio_irq_set_type+0x50/0x530     __irq_set_trigger+0x60/0x184     __setup_irq+0x304/0x6bc     request_threaded_irq+0xc8/0x19c     edge_detector_setup+0x260/0x364     linereq_create+0x420/0x5a8     gpio_ioctl+0x2d4/0x6c0 Fix this by copying the check for GPIO_NO_WAKE_IRQ from qcom-pdc.c, so that MPM is removed entirely from the hierarchy for non-wake GPIOs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-37901</guid>
    </item>
  </channel>
</rss>
