<?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-10-06T03:35:43.758794+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/cve-2024-26938</id>
    <title>CVE-2024-26938 — drm/i915/bios: Tolerate devdata==NULL in intel_bios_encoder_supports_dp_dual_mode()</title>
    <updated>2026-10-06T03:35:43.776420+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/i915/bios: Tolerate devdata==NULL in intel_bios_encoder_supports_dp_dual_mode()</p>
<p>If we have no VBT, or the VBT didn't declare the encoder
in question, we won't have the 'devdata' for the encoder.
Instead of oopsing just bail early.</p>
<p>We won't be able to tell whether the port is DP++ or not,
but so be it.</p>
<p>(cherry picked from commit 26410896206342c8a80d2b027923e9ee7d33b733)</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2024-26938"/>
  </entry>
</feed>
