<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 03:24:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-58007 — soc: qcom: socinfo: Avoid out of bounds read of serial number</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-58007</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;soc: qcom: socinfo: Avoid out of bounds read of serial number&lt;/p&gt;
&lt;p&gt;On MSM8916 devices, the serial number exposed in sysfs is constant and does
not change across individual devices. It&amp;#39;s always:&lt;/p&gt;
&lt;p&gt;db410c:/sys/devices/soc0$ cat serial_number
  2644893864&lt;/p&gt;
&lt;p&gt;The firmware used on MSM8916 exposes SOCINFO_VERSION(0, 8), which does not
have support for the serial_num field in the socinfo struct. There is an
existing check to avoid exposing the serial number in that case, but it&amp;#39;s
not correct: When checking the item_size returned by SMEM, we need to make
sure the *end* of the serial_num is within bounds, instead of comparing
with the *start* offset. The serial_number currently exposed on MSM8916
devices is just an out of bounds read of whatever comes after the socinfo
struct in SMEM.&lt;/p&gt;
&lt;p&gt;Fix this by changing offsetof() to offsetofend(), so that the size of the
field is also taken into account.&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;soc: qcom: socinfo: Avoid out of bounds read of serial number&lt;/p&gt;
&lt;p&gt;On MSM8916 devices, the serial number exposed in sysfs is constant and does
not change across individual devices. It&amp;#39;s always:&lt;/p&gt;
&lt;p&gt;db410c:/sys/devices/soc0$ cat serial_number
  2644893864&lt;/p&gt;
&lt;p&gt;The firmware used on MSM8916 exposes SOCINFO_VERSION(0, 8), which does not
have support for the serial_num field in the socinfo struct. There is an
existing check to avoid exposing the serial number in that case, but it&amp;#39;s
not correct: When checking the item_size returned by SMEM, we need to make
sure the *end* of the serial_num is within bounds, instead of comparing
with the *start* offset. The serial_number currently exposed on MSM8916
devices is just an out of bounds read of whatever comes after the socinfo
struct in SMEM.&lt;/p&gt;
&lt;p&gt;Fix this by changing offsetof() to offsetofend(), so that the size of the
field is also taken into account.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-58007</guid>
    </item>
  </channel>
</rss>
