mailbox: qcom-cpucp: handle NULL data in send_data callback
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mailbox: qcom-cpucp: handle NULL data in send_data callback
mailbox_clear_channel() calls mbox_send_message() with NULL data to notify the remote side that the RX channel has been cleared. qcom_cpucp_mbox_send_data() blindly dereferenced the data pointer, causing a NULL pointer dereference kernel panic when invoked from this path under PREEMPT_RT.
Add an explicit NULL check and return early without writing to the TX register, which is the correct behaviour for a channel-clear notification.
From the CVE record · Linux
The Linux kernel's qcom-cpucp mailbox callback can dereference a NULL pointer when a channel-clear notification is sent under PREEMPT_RT, causing a kernel panic. The input does not specify an attacker path, authentication requirements, or user interaction.
Engineers running Linux kernels that use the qcom-cpucp mailbox under PREEMPT_RT should check; affected versions are not specified.