platform/x86: int3472: Check for adev == NULL
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 5de691bffe57fd0fc2b4dcdcf13815c56d11db10 · < cd2fd6eab480dfc247b737cf7a3d6b009c4d0f1c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
platform/x86: int3472: Check for adev == NULL
Not all devices have an ACPI companion fwnode, so adev might be NULL. This can e.g. (theoretically) happen when a user manually binds one of the int3472 drivers to another i2c/platform device through sysfs.
Add a check for adev not being set and return -ENODEV in that case to avoid a possible NULL pointer deref in skl_int3472_get_acpi_buffer().
From the CVE record · Linux
The int3472 drivers may dereference a NULL pointer when a device has no ACPI companion fwnode. This could occur if a local user manually binds an int3472 driver to another I2C or platform device through sysfs; the description calls this scenario theoretical.
Engineers running the Linux kernel with the int3472 drivers should check whether their kernel includes the fix; affected versions were not specified.