<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T19:13:03.567368+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2024-58007</id>
    <title>CVE-2024-58007 — soc: qcom: socinfo: Avoid out of bounds read of serial number</title>
    <updated>2026-09-29T19:13:04.492040+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>soc: qcom: socinfo: Avoid out of bounds read of serial number</p>
<p>On MSM8916 devices, the serial number exposed in sysfs is constant and does
not change across individual devices. It's always:</p>
<p>db410c:/sys/devices/soc0$ cat serial_number
  2644893864</p>
<p>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'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.</p>
<p>Fix this by changing offsetof() to offsetofend(), so that the size of the
field is also taken into account.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-58007"/>
  </entry>
</feed>
