soc: qcom: socinfo: Avoid out of bounds read of serial number
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0a92feddae0634a0b87c04b19d343f6af97af700, Kernel 22cf4fae6660b6e1a583a41cbf84e3046ca9ccd0, Kernel 2495c6598731b6d7f565140f2bd63ef4bc36ce7d and 5 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.4, >=efb448d0a3fca01bb987dd70963da6185b81751e <0a92feddae0634a0b87c04b19d343f6af97af700, >=efb448d0a3fca01bb987dd70963da6185b81751e <22cf4fae6660b6e1a583a41cbf84e3046ca9ccd0, >=efb448d0a3fca01bb987dd70963da6185b81751e <2495c6598731b6d7f565140f2bd63ef4bc36ce7d, >=efb448d0a3fca01bb987dd70963da6185b81751e <2d09d3c9afa2fc422ac3df7c9b8534f350ee19dd, >=efb448d0a3fca01bb987dd70963da6185b81751e <407c928305c1a37232a63811c400ef616f85ccbc, >=efb448d0a3fca01bb987dd70963da6185b81751e <47470acd719d45c4c8c418c07962f74cc995652b, >=efb448d0a3fca01bb987dd70963da6185b81751e <7445fa05317534bbd8b373c0eff8319187916030, >=efb448d0a3fca01bb987dd70963da6185b81751e <9c88b3a3fae4d60641c3a45be66269d00eff33cd | 0a92feddae0634a0b87c04b19d343f6af97af700, 22cf4fae6660b6e1a583a41cbf84e3046ca9ccd0, 2495c6598731b6d7f565140f2bd63ef4bc36ce7d, 2d09d3c9afa2fc422ac3df7c9b8534f350ee19dd, 407c928305c1a37232a63811c400ef616f85ccbc, 47470acd719d45c4c8c418c07962f74cc995652b, 7445fa05317534bbd8b373c0eff8319187916030, 9c88b3a3fae4d60641c3a45be66269d00eff33cd |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket