<?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 09:55:33 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-56580</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-56580</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-2024-56580</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0254 — 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-2025-avi-0254</link>
      <description>certfr-2025-avi-0254</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0254</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-56580</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-56580</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 105 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: qcom: camss: fix error path on configuration of power domains There is a chance to meet runtime issues during configuration of CAMSS power domains, because on the error path dev_pm_domain_detach() is unexpectedly called with NULL or error pointer. One of the simplest ways to reproduce the problem is to probe CAMSS driver before registration of CAMSS power domains, for instance if a platform CAMCC driver is simply not built. Warning backtrace example:     Unable to handle kernel NULL pointer dereference at virtual address 00000000000001a2     &amp;lt;snip&amp;gt;     pc : dev_pm_domain_detach+0x8/0x48     lr : camss_probe+0x374/0x9c0     &amp;lt;snip&amp;gt;     Call trace:      dev_pm_domain_detach+0x8/0x48      platform_probe+0x70/0xf0      really_probe+0xc4/0x2a8      __driver_probe_device+0x80/0x140      driver_probe_device+0x48/0x170      __device_attach_driver+0xc0/0x148      bus_for_each_drv+0x88/0xf0      __device_attach+0xb0/0x1c0      device_initial_probe+0x1c/0x30      bus_probe_device+0xb4/0xc0      deferred_probe_work_func+0x90/0xd0      process_one_work+0x164/0x3e0      worker_thread+0x310/0x420      kthread+0x120/0x130      ret_from_fork+0x10/0x20&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 105 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: media: qcom: camss: fix error path on configuration of power domains There is a chance to meet runtime issues during configuration of CAMSS power domains, because on the error path dev_pm_domain_detach() is unexpectedly called with NULL or error pointer. One of the simplest ways to reproduce the problem is to probe CAMSS driver before registration of CAMSS power domains, for instance if a platform CAMCC driver is simply not built. Warning backtrace example:     Unable to handle kernel NULL pointer dereference at virtual address 00000000000001a2     &amp;lt;snip&amp;gt;     pc : dev_pm_domain_detach+0x8/0x48     lr : camss_probe+0x374/0x9c0     &amp;lt;snip&amp;gt;     Call trace:      dev_pm_domain_detach+0x8/0x48      platform_probe+0x70/0xf0      really_probe+0xc4/0x2a8      __driver_probe_device+0x80/0x140      driver_probe_device+0x48/0x170      __device_attach_driver+0xc0/0x148      bus_for_each_drv+0x88/0xf0      __device_attach+0xb0/0x1c0      device_initial_probe+0x1c/0x30      bus_probe_device+0xb4/0xc0      deferred_probe_work_func+0x90/0xd0      process_one_work+0x164/0x3e0      worker_thread+0x310/0x420      kthread+0x120/0x130      ret_from_fork+0x10/0x20&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-56580</guid>
    </item>
  </channel>
</rss>
