CVE-2024-58007: soc: qcom: socinfo: Avoid out of bounds read of serial number
First published: Thu Feb 27 2025(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| >=5.4<6.1.129 | ||
| >=6.2<6.6.78 | ||
| >=6.7<6.12.14 | ||
| >=6.13<6.13.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/0a92feddae0634a0b87c04b19d343f6af97af700
- https://git.kernel.org/stable/c/22cf4fae6660b6e1a583a41cbf84e3046ca9ccd0
- https://git.kernel.org/stable/c/407c928305c1a37232a63811c400ef616f85ccbc
- https://git.kernel.org/stable/c/47470acd719d45c4c8c418c07962f74cc995652b
- https://git.kernel.org/stable/c/9c88b3a3fae4d60641c3a45be66269d00eff33cd
- https://git.kernel.org/stable/c/7445fa05317534bbd8b373c0eff8319187916030
- https://git.kernel.org/stable/c/2495c6598731b6d7f565140f2bd63ef4bc36ce7d
- https://git.kernel.org/stable/c/2d09d3c9afa2fc422ac3df7c9b8534f350ee19dd
Frequently Asked Questions
What is the severity of CVE-2024-58007?
CVE-2024-58007 is considered a medium severity vulnerability due to potential information disclosure.
How do I fix CVE-2024-58007?
To fix CVE-2024-58007, update the Linux kernel to a patched version that addresses this vulnerability.
Which versions of the Linux kernel are affected by CVE-2024-58007?
CVE-2024-58007 affects Linux kernel versions between 5.4 and 6.12.14, excluding certain patched versions.
What impact does CVE-2024-58007 have on affected systems?
CVE-2024-58007 can lead to leaking the constant serial number of MSM8916 devices, risking user privacy.
Is CVE-2024-58007 being actively exploited in the wild?
As of now, there are no reports indicating that CVE-2024-58007 is actively exploited in the wild.
- agent/first-publish-date
- agent/type
- agent/title
- agent/references
- agent/author
- agent/source
- agent/description
- agent/guess-ai
- agent/software-canonical-lookup
- agent/weakness
- agent/remedy
- agent/severity
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- agent/softwarecombine
- agent/tags
- agent/event
- collector/mitre-cve
- source/MITRE
- vendor/linux
- canonical/linux kernel
- version/linux kernel/5.4
- version/linux kernel/6.2
- version/linux kernel/6.7
- version/linux kernel/6.13