Bug 2348565 (CVE-2024-58007) - CVE-2024-58007 kernel: soc: qcom: socinfo: Avoid out of bounds read of serial number
Summary: CVE-2024-58007 kernel: soc: qcom: socinfo: Avoid out of bounds read of serial...
Keywords:
Status: NEW
Alias: CVE-2024-58007
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-27 03:03 UTC by OSIDB Bzimport
Modified: 2025-05-13 11:55 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2025:7423 0 None None None 2025-05-13 11:55:15 UTC

Description OSIDB Bzimport 2025-02-27 03:03:26 UTC
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.

Comment 2 errata-xmlrpc 2025-05-13 11:55:13 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:7423 https://access.redhat.com/errata/RHSA-2025:7423


Note You need to log in before you can comment on or make changes to this bug.