mfd: intel_soc_pmic_bxtwc: Use IRQ domain for TMU device
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 957ae5098185e763b5c06be6c3b4b6e98c048712 · < 2310f5336f32eac9ada2d59b965d578efe25c4bf| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mfd: intel_soc_pmic_bxtwc: Use IRQ domain for TMU device
While design wise the idea of converting the driver to use the hierarchy of the IRQ chips is correct, the implementation has (inherited) flaws. This was unveiled when platform_get_irq() had started WARN() on IRQ 0 that is supposed to be a Linux IRQ number (also known as vIRQ).
Rework the driver to respect IRQ domain when creating each MFD device separately, as the domain is not the same for all of them.
From the CVE record · Linux
The Linux kernel's intel_soc_pmic_bxtwc driver does not use the correct IRQ domain for every MFD device, which can trigger a warning when platform_get_irq() encounters IRQ 0. The input does not describe an attacker action or specify whether exploitation requires network access, authentication, or user interaction.
Engineers running the Linux kernel with the intel_soc_pmic_bxtwc driver should check their systems; affected versions are not specified.