<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-17T10:09:27.511273+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2026-99007</id>
    <title>BELL-CVE-2026-99007</title>
    <updated>2026-11-17T10:09:27.526059+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-99007"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1470</id>
    <title>certfr-2026-avi-1470 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
    <updated>2026-11-17T10:09:27.526116+00:00</updated>
    <content>certfr-2026-avi-1470</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-1470"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-396122</id>
    <title>EUVD-2026-396122</title>
    <updated>2026-11-17T10:09:27.526137+00:00</updated>
    <content>EUVD-2026-396122</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-396122"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-99007</id>
    <title>fkie_cve-2026-99007</title>
    <updated>2026-11-17T10:09:27.526149+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN</p>
<p>__drm_fb_helper_initial_config_and_unlock() calls
drm_client_modeset_probe() first, which already fills in each
mode_set-&gt;mode/num_connectors for every connected output, and only
afterwards calls drm_fb_helper_single_fb_probe() to create
fb_helper-&gt;fb and wire it into those mode_sets via
drm_setup_crtcs_fb().</p>
<p>If drm_fb_helper_single_fb_probe() fails with anything other than
-EAGAIN (e.g. dev-&gt;driver-&gt;fbdev_probe() itself fails), the function
bails out before drm_setup_crtcs_fb() runs and before setting
fb_helper-&gt;deferred_setup. The client is left with mode_sets that
have a mode and connectors but mode_set-&gt;fb == NULL, and nothing
marks this fb_helper as needing a retry.</p>
<p>__drm_fb_helper_restore_fbdev_mode_unlocked() only skips committing
when fb_helper-&gt;deferred_setup is set, so a later .restore() call
(drm_lastclose() on process exit, in this report) commits the stale
mode_set through drm_client_modeset_commit() -&gt;
drm_client_modeset_commit_atomic() -&gt; __drm_atomic_helper_set_config(),
which hits WARN_ON(!set-&gt;fb).</p>
<p>Mark fb_helper-&gt;deferred_setup on any drm_fb_helper_single_fb_probe()
failure, not just -EAGAIN, so restore keeps skipping the commit until
a later hotplug event successfully re-probes and re-populates
mode_set-&gt;fb. The real error code is still returned to the caller
unchanged.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-99007"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-g687-j9p7-p4rx</id>
    <title>GHSA-g687-j9p7-p4rx</title>
    <updated>2026-11-17T10:09:27.526198+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN</p>
<p>__drm_fb_helper_initial_config_and_unlock() calls
drm_client_modeset_probe() first, which already fills in each
mode_set-&gt;mode/num_connectors for every connected output, and only
afterwards calls drm_fb_helper_single_fb_probe() to create
fb_helper-&gt;fb and wire it into those mode_sets via
drm_setup_crtcs_fb().</p>
<p>If drm_fb_helper_single_fb_probe() fails with anything other than
-EAGAIN (e.g. dev-&gt;driver-&gt;fbdev_probe() itself fails), the function
bails out before drm_setup_crtcs_fb() runs and before setting
fb_helper-&gt;deferred_setup. The client is left with mode_sets that
have a mode and connectors but mode_set-&gt;fb == NULL, and nothing
marks this fb_helper as needing a retry.</p>
<p>__drm_fb_helper_restore_fbdev_mode_unlocked() only skips committing
when fb_helper-&gt;deferred_setup is set, so a later .restore() call
(drm_lastclose() on process exit, in this report) commits the stale
mode_set through drm_client_modeset_commit() -&gt;
drm_client_modeset_commit_atomic() -&gt; __drm_atomic_helper_set_config(),
which hits WARN_ON(!set-&gt;fb).</p>
<p>Mark fb_helper-&gt;deferred_setup on any drm_fb_helper_single_fb_probe()
failure, not just -EAGAIN, so restore keeps skipping the commit until
a later hotplug event successfully re-probes and re-populates
mode_set-&gt;fb. The real error code is still returned to the caller
unchanged.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-g687-j9p7-p4rx"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-99007</id>
    <title>msrc_CVE-2026-99007 — drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN</title>
    <updated>2026-11-17T10:09:27.526227+00:00</updated>
    <content>msrc_CVE-2026-99007</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-99007"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99007</id>
    <title>UBUNTU-CVE-2026-99007</title>
    <updated>2026-11-17T10:09:27.526243+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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 249 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: drm/fb-helper: defer setup when fbdev_probe() fails, not just on -EAGAIN __drm_fb_helper_initial_config_and_unlock() calls drm_client_modeset_probe() first, which already fills in each mode_set-&gt;mode/num_connectors for every connected output, and only afterwards calls drm_fb_helper_single_fb_probe() to create fb_helper-&gt;fb and wire it into those mode_sets via drm_setup_crtcs_fb(). If drm_fb_helper_single_fb_probe() fails with anything other than -EAGAIN (e.g. dev-&gt;driver-&gt;fbdev_probe() itself fails), the function bails out before drm_setup_crtcs_fb() runs and before setting fb_helper-&gt;deferred_setup. The client is left with mode_sets that have a mode and connectors but mode_set-&gt;fb == NULL, and nothing marks this fb_helper as needing a retry. __drm_fb_helper_restore_fbdev_mode_unlocked() only skips committing when fb_helper-&gt;deferred_setup is set, so a later .restore() call (drm_lastclose() on process exit, in this report) commits the stale mode_set through drm_client_modeset_commit() -&gt; drm_client_modeset_commit_atomic() -&gt; __drm_atomic_helper_set_config(), which hits WARN_ON(!set-&gt;fb). Mark fb_helper-&gt;deferred_setup on any drm_fb_helper_single_fb_probe() failure, not just -EAGAIN, so restore keeps skipping the commit until a later hotplug event successfully re-probes and re-populates mode_set-&gt;fb. The real error code is still returned to the caller unchanged.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-99007"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</id>
    <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-11-17T10:09:27.526519+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152"/>
  </entry>
</feed>
