thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR
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:
thermal/int340x_thermal: handle data_vault when the value is ZERO_SIZE_PTR
In some case, the GDDV returns a package with a buffer which has zero length. It causes that kmemdup() returns ZERO_SIZE_PTR (0x10).
Then the data_vault_read() got NULL point dereference problem when accessing the 0x10 value in data_vault.
[ 71.024560] BUG: kernel NULL pointer dereference, address: 0000000000000010
This patch uses ZERO_OR_NULL_PTR() for checking ZERO_SIZE_PTR or NULL value in data_vault.
From the CVE record · Linux
The Linux kernel’s thermal/int340x_thermal component can dereference an invalid pointer when GDDV returns a package containing a zero-length buffer. This can cause a kernel fault; the input does not establish an attacker path, authentication requirements, or user-interaction conditions.
Engineers running the Linux kernel should check whether their kernel includes the affected thermal/int340x_thermal code; affected versions were not specified.