LiveActive security incident?Get immediate response
CVE Record

CVE-2024-58007: soc: qcom: socinfo: Avoid out of bounds read of serial number

In the Linux kernel, the following vulnerability has been resolved: soc: qcom: socinfo: Avoid out of bounds read of serial number On MSM8916 devices, the serial number exposed in sysfs is constant and does not change across individual devices. It's always: db410c:/sys/devices/soc0$ cat serial_number 2644893864 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. Fix this by changing offsetof() to offsetofend(), so that the size of the field is also taken into account.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2024-58007 is a Linux kernel bug in Qualcomm socinfo handling. On some MSM8916 devices, the reported serial number can come from memory beyond the intended structure, not from a real serial-number field. The known impact is unintended information exposure through sysfs, not confirmed remote compromise.

Executive priority

Treat this as a targeted kernel hygiene issue for embedded Qualcomm Linux assets, not a broad emergency. Patch through normal kernel maintenance, with higher priority where exposed devices are shared, multi-user, or difficult to physically control.

Technical view

The Qualcomm socinfo driver checked the start offset of serial_num against the SMEM item size, but not the field end. For SOCINFO_VERSION(0, 8), serial_num is unsupported, so reading /sys/devices/soc0/serial_number can expose adjacent SMEM data. Stable fixes change offsetof() to offsetofend().

Likely exposure

Exposure appears limited to Linux systems using the Qualcomm socinfo driver on affected SoCs, especially MSM8916-class devices exposing /sys/devices/soc0/serial_number. The source bundle does not identify broad server, cloud, or generic desktop exposure.

Exploitation context

The bundle does not show KEV listing, public exploitation, or exploit tooling. The described behavior is a local information disclosure through a sysfs attribute, requiring access to read the exposed serial_number path.

Researcher notes

Evidence supports an out-of-bounds read caused by a bounds-check error in socinfo serial_num handling. The bundle does not provide CVSS, CWE mapping, exploit confirmation, or detailed fixed-version ranges beyond stable commit references and Debian advisories.

Mitigation direction

  • Update to a vendor or distribution kernel containing the referenced stable fix.
  • Track Debian LTS advisories if managing Debian-based affected kernels.
  • Prioritize Qualcomm MSM8916 or similar embedded device fleets for review.
  • Check device vendor firmware and kernel guidance before assuming fixed versions.
  • Limit unnecessary local access to affected devices until patched.

Validation and detection

  • Inventory Linux devices using Qualcomm socinfo support.
  • Identify kernels matching affected lines in the CVE source bundle.
  • Check whether /sys/devices/soc0/serial_number is present on candidate devices.
  • Confirm the running kernel includes the stable commit changing offsetof() to offsetofend().
  • Review Debian LTS advisory coverage for managed Debian systems.
Prepared
Confidence
medium
Sources
12

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-58007 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
11Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxefb448d0a3fca01bb987dd70963da6185b81751e, efb448d0a3fca01bb987dd70963da6185b81751e, efb448d0a3fca01bb987dd70963da6185b81751e, efb448d0a3fca01bb987dd70963da6185b81751e, efb448d0a3fca01bb987dd70963da6185b81751e, efb448d0a3fca01bb987dd70963da6185b81751e, efb448d0a3fca01bb987dd70963da6185b81751e, efb448d0a3fca01bb987dd70963da6185b81751eunaffected
LinuxLinux5.4, 0, 5.4.291, 5.10.235, 5.15.179, 6.1.129, 6.6.78, 6.12.14, 6.13.3, 6.14affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.