firmware: qcom: scm: Cleanup global '__scm' on probe failures
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1e76b546e6fca7eb568161f408133904ca6bcf4f, Kernel 390d3baeba51a126f75c97b90ec28b9384ce4b84 and Kernel faf1715798fe72b79e4432ce8c6d03ca69765425.
In the Linux kernel, the following vulnerability has been resolved: firmware: qcom: scm: Cleanup global '__scm' on probe failures If SCM driver fails the probe, it should not leave global '__scm' variable assigned, because external users of this driver will assume the probe finished successfully. For example TZMEM parts ('__scm->mempool') are initialized later in the probe, but users of it (__scm_smc_call()) rely on the '__scm' variable. This fixes theoretical NULL pointer exception, triggered via introducing probe deferral in SCM driver with call trace: qcom_tzmem_alloc+0x70/0x1ac (P) qcom_tzmem_alloc+0x64/0x1ac (L) qcom_scm_assign_mem+0x78/0x194 qcom_rmtfs_mem_probe+0x2d4/0x38c platform_probe+0x68/0xc8
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.11, >=40289e35ca525f29a03989352ab207b6a9675475 <1e76b546e6fca7eb568161f408133904ca6bcf4f, >=40289e35ca525f29a03989352ab207b6a9675475 <390d3baeba51a126f75c97b90ec28b9384ce4b84, >=40289e35ca525f29a03989352ab207b6a9675475 <faf1715798fe72b79e4432ce8c6d03ca69765425 | 1e76b546e6fca7eb568161f408133904ca6bcf4f, 390d3baeba51a126f75c97b90ec28b9384ce4b84, faf1715798fe72b79e4432ce8c6d03ca69765425 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket