<?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:37:15 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38354</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38354</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-38354</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0698 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0698</link>
      <description>certfr-2025-avi-0698</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0698</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38354</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38354</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 122 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/msm/gpu: Fix crash when throttling GPU immediately during boot There is a small chance that the GPU is already hot during boot. In that case, the call to of_devfreq_cooling_register() will immediately try to apply devfreq cooling, as seen in the following crash:   Unable to handle kernel paging request at virtual address 0000000000014110   pc : a6xx_gpu_busy+0x1c/0x58 [msm]   lr : msm_devfreq_get_dev_status+0xbc/0x140 [msm]   Call trace:    a6xx_gpu_busy+0x1c/0x58 [msm] (P)    devfreq_simple_ondemand_func+0x3c/0x150    devfreq_update_target+0x44/0xd8    qos_max_notifier_call+0x30/0x84    blocking_notifier_call_chain+0x6c/0xa0    pm_qos_update_target+0xd0/0x110    freq_qos_apply+0x3c/0x74    apply_constraint+0x88/0x148    __dev_pm_qos_update_request+0x7c/0xcc    dev_pm_qos_update_request+0x38/0x5c    devfreq_cooling_set_cur_state+0x98/0xf0    __thermal_cdev_update+0x64/0xb4    thermal_cdev_update+0x4c/0x58    step_wise_manage+0x1f0/0x318    __thermal_zone_device_update+0x278/0x424    __thermal_cooling_device_register+0x2bc/0x308    thermal_of_cooling_device_register+0x10/0x1c    of_devfreq_cooling_register_power+0x240/0x2bc    of_devfreq_cooling_register+0x14/0x20    msm_devfreq_init+0xc4/0x1a0 [msm]    msm_gpu_init+0x304/0x574 [msm]    adreno_gpu_init+0x1c4/0x2e0 [msm]    a6xx_gpu_init+0x5c8/0x9c8 [msm]    adreno_bind+0x2a8/0x33c [msm]    ... At this point we haven&amp;#39;t initialized the GMU at all yet, so we…&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 122 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/msm/gpu: Fix crash when throttling GPU immediately during boot There is a small chance that the GPU is already hot during boot. In that case, the call to of_devfreq_cooling_register() will immediately try to apply devfreq cooling, as seen in the following crash:   Unable to handle kernel paging request at virtual address 0000000000014110   pc : a6xx_gpu_busy+0x1c/0x58 [msm]   lr : msm_devfreq_get_dev_status+0xbc/0x140 [msm]   Call trace:    a6xx_gpu_busy+0x1c/0x58 [msm] (P)    devfreq_simple_ondemand_func+0x3c/0x150    devfreq_update_target+0x44/0xd8    qos_max_notifier_call+0x30/0x84    blocking_notifier_call_chain+0x6c/0xa0    pm_qos_update_target+0xd0/0x110    freq_qos_apply+0x3c/0x74    apply_constraint+0x88/0x148    __dev_pm_qos_update_request+0x7c/0xcc    dev_pm_qos_update_request+0x38/0x5c    devfreq_cooling_set_cur_state+0x98/0xf0    __thermal_cdev_update+0x64/0xb4    thermal_cdev_update+0x4c/0x58    step_wise_manage+0x1f0/0x318    __thermal_zone_device_update+0x278/0x424    __thermal_cooling_device_register+0x2bc/0x308    thermal_of_cooling_device_register+0x10/0x1c    of_devfreq_cooling_register_power+0x240/0x2bc    of_devfreq_cooling_register+0x14/0x20    msm_devfreq_init+0xc4/0x1a0 [msm]    msm_gpu_init+0x304/0x574 [msm]    adreno_gpu_init+0x1c4/0x2e0 [msm]    a6xx_gpu_init+0x5c8/0x9c8 [msm]    adreno_bind+0x2a8/0x33c [msm]    ... At this point we haven&amp;#39;t initialized the GMU at all yet, so we…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38354</guid>
    </item>
  </channel>
</rss>
