<?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 02:02:27 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38601</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38601</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-38601</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0787 — 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-2025-avi-0787</link>
      <description>certfr-2025-avi-0787</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0787</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38601</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38601</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 161 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: clear initialized flag for deinit-ed srng lists In a number of cases we see kernel panics on resume due to ath11k kernel page fault, which happens under the following circumstances: 1) First ath11k_hal_dump_srng_stats() call  Last interrupt received for each group:  ath11k_pci 0000:01:00.0: group_id 0 22511ms before  ath11k_pci 0000:01:00.0: group_id 1 14440788ms before  [..]  ath11k_pci 0000:01:00.0: failed to receive control response completion, polling..  ath11k_pci 0000:01:00.0: Service connect timeout  ath11k_pci 0000:01:00.0: failed to connect to HTT: -110  ath11k_pci 0000:01:00.0: failed to start core: -110  ath11k_pci 0000:01:00.0: firmware crashed: MHI_CB_EE_RDDM  ath11k_pci 0000:01:00.0: already resetting count 2  ath11k_pci 0000:01:00.0: failed to wait wlan mode request (mode 4): -110  ath11k_pci 0000:01:00.0: qmi failed to send wlan mode off: -110  ath11k_pci 0000:01:00.0: failed to reconfigure driver on crash recovery  [..] 2) At this point reconfiguration fails (we have 2 resets) and   ath11k_core_reconfigure_on_crash() calls ath11k_hal_srng_deinit()   which destroys srng lists.  However, it does not reset per-list   -&amp;gt;initialized flag. 3) Second ath11k_hal_dump_srng_stats() call sees stale -&amp;gt;initialized   flag and attempts to dump srng stats:  Last interrupt received for each group:  ath11k_pci 0000:01:00.0: group_id 0 66785ms before  ath11k_pci 0000:01:00.0: group_id 1 14485062m…&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 161 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: clear initialized flag for deinit-ed srng lists In a number of cases we see kernel panics on resume due to ath11k kernel page fault, which happens under the following circumstances: 1) First ath11k_hal_dump_srng_stats() call  Last interrupt received for each group:  ath11k_pci 0000:01:00.0: group_id 0 22511ms before  ath11k_pci 0000:01:00.0: group_id 1 14440788ms before  [..]  ath11k_pci 0000:01:00.0: failed to receive control response completion, polling..  ath11k_pci 0000:01:00.0: Service connect timeout  ath11k_pci 0000:01:00.0: failed to connect to HTT: -110  ath11k_pci 0000:01:00.0: failed to start core: -110  ath11k_pci 0000:01:00.0: firmware crashed: MHI_CB_EE_RDDM  ath11k_pci 0000:01:00.0: already resetting count 2  ath11k_pci 0000:01:00.0: failed to wait wlan mode request (mode 4): -110  ath11k_pci 0000:01:00.0: qmi failed to send wlan mode off: -110  ath11k_pci 0000:01:00.0: failed to reconfigure driver on crash recovery  [..] 2) At this point reconfiguration fails (we have 2 resets) and   ath11k_core_reconfigure_on_crash() calls ath11k_hal_srng_deinit()   which destroys srng lists.  However, it does not reset per-list   -&amp;gt;initialized flag. 3) Second ath11k_hal_dump_srng_stats() call sees stale -&amp;gt;initialized   flag and attempts to dump srng stats:  Last interrupt received for each group:  ath11k_pci 0000:01:00.0: group_id 0 66785ms before  ath11k_pci 0000:01:00.0: group_id 1 14485062m…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38601</guid>
    </item>
  </channel>
</rss>
