CVE-2023-52765
published 2024-05-21CVE-2023-52765: In the Linux kernel, the following vulnerability has been resolved: mfd: qcom-spmi-pmic: Fix revid implementation The Qualcomm SPMI PMIC revid implementation…
PriorityP423medium6.2CVSS 3.1
AVLACLPRNUINSUCNINAH
EPSS
0.25%
16.6th percentile
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
12 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.64-1 (bookworm) | linux 6.1.64-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= e9c11c6e3a0e93903f5a13f8d2f97ae1bba512e1 < db98de0809f12b0edb9cd1be78e1ec1bfeba8f40 | db98de0809f12b0edb9cd1be78e1ec1bfeba8f40 |
| linux | linux | >= e9c11c6e3a0e93903f5a13f8d2f97ae1bba512e1 < 4ce77b023d42a9f1062eecf438df1af4b4072eb2 | 4ce77b023d42a9f1062eecf438df1af4b4072eb2 |
| linux | linux | >= e9c11c6e3a0e93903f5a13f8d2f97ae1bba512e1 < affae18838db5e6b463ee30c821385695af56dc2 | affae18838db5e6b463ee30c821385695af56dc2 |
| linux | linux | >= e9c11c6e3a0e93903f5a13f8d2f97ae1bba512e1 < 7b439aaa62fee474a0d84d67a25f4984467e7b95 | 7b439aaa62fee474a0d84d67a25f4984467e7b95 |
| linux | linux_kernel | >= 0 < 6.1.64-1 | 6.1.64-1 |
| linux | linux_kernel | >= 0 < 6.6.8-1 | 6.6.8-1 |
| linux | linux_kernel | >= 0 < 6.6.8-1 | 6.6.8-1 |
| linux | linux_kernel | >= 6.0 < 6.1.64 | 6.1.64 |
| linux | linux_kernel | >= 6.2 < 6.5.13 | 6.5.13 |
| linux | linux_kernel | >= 6.6 < 6.6.3 | 6.6.3 |
CVSS provenance
nvdv3.16.2MEDIUMCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
osv6.2MEDIUM
vendor_debian6.2MEDIUM
vendor_redhat6.2MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-wgf9-7m97-x4xg: In the Linux kernel, the following vulnerability has been resolved:
mfd: qcom-spmi-pmic: Fix revid implementation
The Qualcomm SPMI PMIC revid imple
ghsa_unreviewed·2024-05-21
CVE-2023-52765 [MEDIUM] CWE-476 GHSA-wgf9-7m97-x4xg: In the Linux kernel, the following vulnerability has been resolved:
mfd: qcom-spmi-pmic: Fix revid implementation
The Qualcomm SPMI PMIC revid imple
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_
OSV
CVE-2023-52765: In the Linux kernel, the following vulnerability has been resolved: mfd: qcom-spmi-pmic: Fix revid implementation The Qualcomm SPMI PMIC revid impleme
osv·2024-05-21·CVSS 6.2
CVE-2023-52765 [MEDIUM] CVE-2023-52765: In the Linux kernel, the following vulnerability has been resolved: mfd: qcom-spmi-pmic: Fix revid implementation The Qualcomm SPMI PMIC revid impleme
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()
Red Hat
kernel: mfd: qcom-spmi-pmic: Fix revid implementation
vendor_redhat·2024-05-21·CVSS 6.2
CVE-2023-52765 [MEDIUM] CWE-413 kernel: mfd: qcom-spmi-pmic: Fix revid implementation
kernel: mfd: qcom-spmi-pmic: Fix revid implementation
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 dev
Debian
CVE-2023-52765: linux - In the Linux kernel, the following vulnerability has been resolved: mfd: qcom-s...
vendor_debian·2023·CVSS 6.2
CVE-2023-52765 [MEDIUM] CVE-2023-52765: linux - In the Linux kernel, the following vulnerability has been resolved: mfd: qcom-s...
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()
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/4ce77b023d42a9f1062eecf438df1af4b4072eb2https://git.kernel.org/stable/c/7b439aaa62fee474a0d84d67a25f4984467e7b95https://git.kernel.org/stable/c/affae18838db5e6b463ee30c821385695af56dc2https://git.kernel.org/stable/c/db98de0809f12b0edb9cd1be78e1ec1bfeba8f40https://git.kernel.org/stable/c/4ce77b023d42a9f1062eecf438df1af4b4072eb2https://git.kernel.org/stable/c/7b439aaa62fee474a0d84d67a25f4984467e7b95https://git.kernel.org/stable/c/affae18838db5e6b463ee30c821385695af56dc2https://git.kernel.org/stable/c/db98de0809f12b0edb9cd1be78e1ec1bfeba8f40
2024-05-21
Published