CVE-2023-52765

Summary

In the Linux kernel, the following vulnerability has been resolved:

mfd: qcom-spmi-pmic: Fix revid implementation

The Qualcomm SPMI PMIC revid implementation is broken in multiple ways.

First, it assumes that just because the sibling base device has been registered that means that it is also bound to a driver, which may not be the case (e.g. due to probe deferral or asynchronous probe). This could trigger a NULL-pointer dereference when attempting to access the driver data of the unbound device.

Second, it accesses driver data of a sibling device directly and without any locking, which means that the driver data may be freed while it is being accessed (e.g. on driver unbind).

Third, it leaks a struct device reference to the sibling device which is looked up using the spmi_device_from_of() every time a function (child) device is calling the revid function (e.g. on probe).

Fix this mess by reimplementing the revid lookup so that it is done only at probe of the PMIC device; the base device fetches the revid info from the hardware, while any secondary SPMI device fetches the information from the base device and caches it so that it can be accessed safely from its children. If the base device has not been probed yet then probe of a secondary device is deferred.

Affected Software

VendorProductVersion RangeStatus
LinuxLinuxe9c11c6e3a0e93903f5a13f8d2f97ae1bba512e1 < db98de0809f12b0edb9cd1be78e1ec1bfeba8f40affected
LinuxLinuxe9c11c6e3a0e93903f5a13f8d2f97ae1bba512e1 < 4ce77b023d42a9f1062eecf438df1af4b4072eb2affected
LinuxLinuxe9c11c6e3a0e93903f5a13f8d2f97ae1bba512e1 < affae18838db5e6b463ee30c821385695af56dc2affected
LinuxLinuxe9c11c6e3a0e93903f5a13f8d2f97ae1bba512e1 < 7b439aaa62fee474a0d84d67a25f4984467e7b95affected
LinuxLinux6.0affected
LinuxLinux0 < 6.0unaffected
LinuxLinux6.1.64 <= 6.1.*unaffected
LinuxLinux6.5.13 <= 6.5.*unaffected
LinuxLinux6.6.3 <= 6.6.*unaffected
LinuxLinux6.7 <= *unaffected

Weaknesses

ADP Enrichment

CISA ADP Vulnrichment

  • SSVC:
  • Exploitation: none
    • Automatable: no
    • Technical Impact: partial

CVE Program Container

Additional References

References