<?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://cve.radiocsirt.org</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>Mon, 05 Oct 2026 08:27:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80937 — wifi: mt76: mt7915: bound the device EEPROM address before the EFUSE copy</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-80937</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: mt76: mt7915: bound the device EEPROM address before the EFUSE copy&lt;/p&gt;
&lt;p&gt;mt7915_mcu_get_eeprom() copies a fixed EFUSE block into the driver&amp;#39;s
dev-&amp;gt;mt76.eeprom.data buffer at the offset reported by the MCU response
(res-&amp;gt;addr, a device-controlled __le32) without checking it against the
buffer size. A malicious or malfunctioning device can report an arbitrary
address and drive a 16-byte out-of-bounds write past eeprom.data.&lt;/p&gt;
&lt;p&gt;Reject a response whose address would place the copy outside eeprom.data
before deriving the destination pointer. Devices that echo the requested
in-bounds offset are unaffected.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: mt76: mt7915: bound the device EEPROM address before the EFUSE copy&lt;/p&gt;
&lt;p&gt;mt7915_mcu_get_eeprom() copies a fixed EFUSE block into the driver&amp;#39;s
dev-&amp;gt;mt76.eeprom.data buffer at the offset reported by the MCU response
(res-&amp;gt;addr, a device-controlled __le32) without checking it against the
buffer size. A malicious or malfunctioning device can report an arbitrary
address and drive a 16-byte out-of-bounds write past eeprom.data.&lt;/p&gt;
&lt;p&gt;Reject a response whose address would place the copy outside eeprom.data
before deriving the destination pointer. Devices that echo the requested
in-bounds offset are unaffected.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-80937</guid>
    </item>
  </channel>
</rss>
