CyberSecBulletin
CVE-2024-58007NVD status: Modified

Linux: Out-of-bounds Read

CVE-2024-58007 is a high-severity out-of-bounds read vulnerability in Linux, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 7445fa05317534bbd8b373c0eff8319187916030, 2495c6598731b6d7f565140f2bd63ef4bc36ce7d, 2d09d3c9afa2fc422ac3df7c9b8534f350ee19dd as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.25% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 7445fa05317534bbd8b373c0eff8319187916030 or 2495c6598731b6d7f565140f2bd63ef4bc36ce7d or 2d09d3c9afa2fc422ac3df7c9b8534f350ee19dd or 9c88b3a3fae4d60641c3a45be66269d00eff33cd, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.1.129 or 6.6.78 or 6.12.14 or 6.13.3, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxefb448d0a3fca01bb987dd70963da6185b81751e up to, but not including, 7445fa05317534bbd8b373c0eff8319187916030; efb448d0a3fca01bb987dd70963da6185b81751e up to, but not including, 2495c6598731b6d7f565140f2bd63ef4bc36ce7d; efb448d0a3fca01bb987dd70963da6185b81751e up to, but not including, 2d09d3c9afa2fc422ac3df7c9b8534f350ee19dd; efb448d0a3fca01bb987dd70963da6185b81751e up to, but not including, 9c88b3a3fae4d60641c3a45be66269d00eff33cd; efb448d0a3fca01bb987dd70963da6185b81751e up to, but not including, 47470acd719d45c4c8c418c07962f74cc995652b; efb448d0a3fca01bb987dd70963da6185b81751e up to, but not including, 407c928305c1a37232a63811c400ef616f85ccbc; efb448d0a3fca01bb987dd70963da6185b81751e up to, but not including, 0a92feddae0634a0b87c04b19d343f6af97af700; efb448d0a3fca01bb987dd70963da6185b81751e up to, but not including, 22cf4fae6660b6e1a583a41cbf84e3046ca9ccd0; and 1 more ranges7445fa05317534bbd8b373c0eff8319187916030, 2495c6598731b6d7f565140f2bd63ef4bc36ce7d, 2d09d3c9afa2fc422ac3df7c9b8534f350ee19dd, 9c88b3a3fae4d60641c3a45be66269d00eff33cd, 47470acd719d45c4c8c418c07962f74cc995652b, 407c928305c1a37232a63811c400ef616f85ccbc
LinuxLinux Kernel5.4 up to, but not including, 6.1.129; 6.2 up to, but not including, 6.6.78; 6.7 up to, but not including, 6.12.14; 6.13 up to, but not including, 6.13.36.1.129, 6.6.78, 6.12.14, 6.13.3

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. Scored by NVD.

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Read

The product reads data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that provides appropriate memory abstractions.

More Out-of-bounds Read vulnerabilities (CWE-125)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Read vulnerabilities

Spotted an error? Tell us.