CVE-2024-46693

In the Linux kernel, the following vulnerability has been resolved: soc: qcom: pmic_glink: Fix race during initialization As pointed out by Stephen Boyd it is possible that during initialization of the pmic_glink child drivers, the protection-domain notifiers fires, and the associated work is scheduled, before the client registration returns and as a result the local "client" pointer has been initialized. The outcome of this is a NULL pointer dereference as the "client" pointer is blindly dereferenced. Timeline provided by Stephen: CPU0 CPU1 ---- ---- ucsi->client = NULL; devm_pmic_glink_register_client() client->pdr_notify(client->priv, pg->client_state) pmic_glink_ucsi_pdr_notify() schedule_work(&ucsi->register_work) <schedule away> pmic_glink_ucsi_register() ucsi_register() pmic_glink_ucsi_read_version() pmic_glink_ucsi_read() pmic_glink_ucsi_read() pmic_glink_send(ucsi->client) <client is NULL BAD> ucsi->client = client // Too late! This code is identical across the altmode, battery manager and usci child drivers. Resolve this by splitting the allocation of the "client" object and the registration thereof into two operations. This only happens if the protection domain registry is populated at the time of registration, which by the introduction of commit '1ebcde047c54 ("soc: qcom: add pd-mapper implementation")' became much more likely.
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.11:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.11:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.11:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.11:rc5:*:*:*:*:*:*

History

13 Sep 2024, 16:52

Type Values Removed Values Added
First Time Linux linux Kernel
Linux
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 4.7
CPE cpe:2.3:o:linux:linux_kernel:6.11:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.11:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.11:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.11:rc5:*:*:*:*:*:*
References () https://git.kernel.org/stable/c/1efdbf5323c9360e05066049b97414405e94e087 - () https://git.kernel.org/stable/c/1efdbf5323c9360e05066049b97414405e94e087 - Patch
References () https://git.kernel.org/stable/c/3568affcddd68743e25aa3ec1647d9b82797757b - () https://git.kernel.org/stable/c/3568affcddd68743e25aa3ec1647d9b82797757b - Patch
References () https://git.kernel.org/stable/c/943b0e7cc646a624bb20a68080f8f1a4a55df41c - () https://git.kernel.org/stable/c/943b0e7cc646a624bb20a68080f8f1a4a55df41c - Patch
CWE CWE-476

13 Sep 2024, 14:06

Type Values Removed Values Added
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: soc: qcom: pmic_glink: Corrección de la ejecución durante la inicialización Como señaló Stephen Boyd, es posible que durante la inicialización de los controladores secundarios pmic_glink, se activen los notificadores del dominio de protección y se programe el trabajo asociado, antes de que vuelva el registro del cliente y, como resultado, se haya inicializado el puntero "cliente" local. El resultado de esto es una desreferencia de puntero NULL ya que el puntero "cliente" se desreferencia ciegamente. Cronología proporcionada por Stephen: CPU0 CPU1 ---- ---- ucsi-&gt;client = NULL; devm_pmic_glink_register_client() client-&gt;pdr_notify(client-&gt;priv, pg-&gt;client_state) pmic_glink_ucsi_pdr_notify() schedule_work(&amp;ucsi-&gt;register_work) pmic_glink_ucsi_register() ucsi_register() pmic_glink_ucsi_read_version() pmic_glink_ucsi_read() pmic_glink_ucsi_read() pmic_glink_send(ucsi-&gt;client) ucsi-&gt;client = client // ¡Demasiado tarde! Este código es idéntico en los controladores secundarios altmode, battery manager y usci. Resuelva esto dividiendo la asignación del objeto "cliente" y su registro en dos operaciones. Esto solo sucede si el registro del dominio de protección se completa al momento del registro, lo que se volvió mucho más probable con la introducción del commit '1ebcde047c54 ("soc: qcom: add pd-mapper implementation").

13 Sep 2024, 06:15

Type Values Removed Values Added
New CVE

Information

Published : 2024-09-13 06:15

Updated : 2024-09-13 16:52


NVD link : CVE-2024-46693

Mitre link : CVE-2024-46693

CVE.ORG link : CVE-2024-46693


JSON object : View

Products Affected

linux

  • linux_kernel
CWE
CWE-476

NULL Pointer Dereference