<?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 03:59:34 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2024-26874</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2024-26874</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-2024-26874</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0381 — De multiples vulnérabilités ont été découvertes dans &lt;span
class="textit"&gt;le noyau Linux de Debian&lt;/span&gt;. Elles permet…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2024-avi-0381</link>
      <description>certfr-2024-avi-0381</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2024-avi-0381</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-26874</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26874</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 164 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Fix a null pointer crash in mtk_drm_crtc_finish_page_flip It&amp;#39;s possible that mtk_crtc-&amp;gt;event is NULL in mtk_drm_crtc_finish_page_flip(). pending_needs_vblank value is set by mtk_crtc-&amp;gt;event, but in mtk_drm_crtc_atomic_flush(), it&amp;#39;s is not guarded by the same lock in mtk_drm_finish_page_flip(), thus a race condition happens. Consider the following case: CPU1                              CPU2 step 1: mtk_drm_crtc_atomic_begin() mtk_crtc-&amp;gt;event is not null,                                   step 1:                                   mtk_drm_crtc_atomic_flush:                                   mtk_drm_crtc_update_config(                                       !!mtk_crtc-&amp;gt;event) step 2: mtk_crtc_ddp_irq -&amp;gt; mtk_drm_finish_page_flip: lock mtk_crtc-&amp;gt;event set to null, pending_needs_vblank set to false unlock                                   pending_needs_vblank set to true,                                   step 2:                                   mtk_crtc_ddp_irq -&amp;gt;                                   mtk_drm_finish_page_flip called again,                                   pending_needs_vblank is still true                                   //null pointer Instead of guarding the entire mtk_drm_crtc_atomic_flush(), it&amp;#39;s more efficient to just check if mtk_crtc-&amp;gt;event is null before use.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 164 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Fix a null pointer crash in mtk_drm_crtc_finish_page_flip It&amp;#39;s possible that mtk_crtc-&amp;gt;event is NULL in mtk_drm_crtc_finish_page_flip(). pending_needs_vblank value is set by mtk_crtc-&amp;gt;event, but in mtk_drm_crtc_atomic_flush(), it&amp;#39;s is not guarded by the same lock in mtk_drm_finish_page_flip(), thus a race condition happens. Consider the following case: CPU1                              CPU2 step 1: mtk_drm_crtc_atomic_begin() mtk_crtc-&amp;gt;event is not null,                                   step 1:                                   mtk_drm_crtc_atomic_flush:                                   mtk_drm_crtc_update_config(                                       !!mtk_crtc-&amp;gt;event) step 2: mtk_crtc_ddp_irq -&amp;gt; mtk_drm_finish_page_flip: lock mtk_crtc-&amp;gt;event set to null, pending_needs_vblank set to false unlock                                   pending_needs_vblank set to true,                                   step 2:                                   mtk_crtc_ddp_irq -&amp;gt;                                   mtk_drm_finish_page_flip called again,                                   pending_needs_vblank is still true                                   //null pointer Instead of guarding the entire mtk_drm_crtc_atomic_flush(), it&amp;#39;s more efficient to just check if mtk_crtc-&amp;gt;event is null before use.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2024-26874</guid>
    </item>
  </channel>
</rss>
