CVE-2024-58007: soc: qcom: socinfo: Avoid out of bounds read of serial number
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0a92feddae0634a0b87c04b19d343f6af97af700, 22cf4fae6660b6e1a583a41cbf84e3046ca9ccd0, 2495c6598731b6d7f565140f2bd63ef4bc36ce7d; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.78.1-3.
Low priority for now. Upgrade to Linux Linux 0a92feddae0634a0b87c04b19d343f6af97af700, 22cf4fae6660b6e1a583a41cbf84e3046ca9ccd0, 2495c6598731b6d7f565140f2bd63ef4bc36ce7d; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.78.1-3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 26, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-125
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.4 and later · before 6.1.129
- linux linux kernel6.2 and later · before 6.6.78
- linux linux kernel6.7 and later · before 6.12.14
- linux linux kernel6.13 and later · before 6.13.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.4affected
- efb448d0a3fca01bb987dd70963da6185b81751e and later · before 7445fa05317534bbd8b373c0eff8319187916030affected · git
- efb448d0a3fca01bb987dd70963da6185b81751e and later · before 2495c6598731b6d7f565140f2bd63ef4bc36ce7daffected · git
- efb448d0a3fca01bb987dd70963da6185b81751e and later · before 2d09d3c9afa2fc422ac3df7c9b8534f350ee19ddaffected · git
- efb448d0a3fca01bb987dd70963da6185b81751e and later · before 9c88b3a3fae4d60641c3a45be66269d00eff33cdaffected · git
- efb448d0a3fca01bb987dd70963da6185b81751e and later · before 47470acd719d45c4c8c418c07962f74cc995652baffected · git
- efb448d0a3fca01bb987dd70963da6185b81751e and later · before 407c928305c1a37232a63811c400ef616f85ccbcaffected · git
- efb448d0a3fca01bb987dd70963da6185b81751e and later · before 0a92feddae0634a0b87c04b19d343f6af97af700affected · git
- efb448d0a3fca01bb987dd70963da6185b81751e and later · before 22cf4fae6660b6e1a583a41cbf84e3046ca9ccd0affected · git
- before 5.4not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.56.1.el10_2 | 6.12.0-211.56.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-58003Feb 26, 2025 · media: i2c: ds90ub9x3: Fix extra fwnode_handle_put()31Monitor
- ← EarlierCVE-2024-58004Feb 26, 2025 · media: intel/ipu6: remove cpu latency qos request on error31Monitor
- Later →CVE-2024-58008Feb 26, 2025 · KEYS: trusted: dcp: fix improper sg use with CONFIG_VMAP_STACK=y22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0a92feddae0634a0b87c04b19d343f6af97af700 | Vendor (CNA) |
| Linux Linux | 22cf4fae6660b6e1a583a41cbf84e3046ca9ccd0 | Vendor (CNA) |
| Linux Linux | 2495c6598731b6d7f565140f2bd63ef4bc36ce7d | Vendor (CNA) |
| Linux Linux | 2d09d3c9afa2fc422ac3df7c9b8534f350ee19dd | Vendor (CNA) |
| Linux Linux | 407c928305c1a37232a63811c400ef616f85ccbc | Vendor (CNA) |
| Linux Linux | 47470acd719d45c4c8c418c07962f74cc995652b | Vendor (CNA) |
| Linux Linux | 7445fa05317534bbd8b373c0eff8319187916030 | Vendor (CNA) |
| Linux Linux | 9c88b3a3fae4d60641c3a45be66269d00eff33cd | Vendor (CNA) |
| azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 | 6.6.78.1-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 5.14.0-570.16.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-570.16.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-570.16.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-570.16.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-570.16.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-570.16.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-570.16.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-570.16.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-570.16.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-570.16.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-570.16.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 5.14.0-570.16.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.1.129-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-570.16.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-570.16.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-570.16.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-570.16.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-570.16.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-570.16.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-570.16.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-570.16.1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+5
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/22cf4fae6660b6e1a583a41cbf84e3046ca9ccd0
- git.kernel.org/stable/c/2495c6598731b6d7f565140f2bd63ef4bc36ce7d
- git.kernel.org/stable/c/2d09d3c9afa2fc422ac3df7c9b8534f350ee19dd
- git.kernel.org/stable/c/407c928305c1a37232a63811c400ef616f85ccbc
- git.kernel.org/stable/c/47470acd719d45c4c8c418c07962f74cc995652b
- git.kernel.org/stable/c/7445fa05317534bbd8b373c0eff8319187916030
- git.kernel.org/stable/c/9c88b3a3fae4d60641c3a45be66269d00eff33cd
- lists.debian.org/debian-lts-announce/2025/03/msg00028.html
- lists.debian.org/debian-lts-announce/2025/05/msg00030.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.