<?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-06T21:44:53.612752+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-53063</id>
    <title>CVE-2024-53063 — media: dvbdev: prevent the risk of out of memory access</title>
    <updated>2026-10-06T21:44:53.629079+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>media: dvbdev: prevent the risk of out of memory access</p>
<p>The dvbdev contains a static variable used to store dvb minors.</p>
<p>The behavior of it depends if CONFIG_DVB_DYNAMIC_MINORS is set
or not. When not set, dvb_register_device() won't check for
boundaries, as it will rely that a previous call to
dvb_register_adapter() would already be enforcing it.</p>
<p>On a similar way, dvb_device_open() uses the assumption
that the register functions already did the needed checks.</p>
<p>This can be fragile if some device ends using different
calls. This also generate warnings on static check analysers
like Coverity.</p>
<p>So, add explicit guards to prevent potential risk of OOM issues.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2024-53063"/>
  </entry>
</feed>
