power: supply: bq27xxx-i2c: Do not free non existing IRQ
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 444ff00734f3878cd54ddd1ed5e2e6dbea9326d5 · < fbca8bae1ba79d443a58781b45e92a73a24ac8f8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
power: supply: bq27xxx-i2c: Do not free non existing IRQ
The bq27xxx i2c-client may not have an IRQ, in which case client->irq will be 0. bq27xxx_battery_i2c_probe() already has an if (client->irq) check wrapping the request_threaded_irq().
But bq27xxx_battery_i2c_remove() unconditionally calls free_irq(client->irq) leading to:
[ 190.310742] ------------[ cut here ]------------ [ 190.310843] Trying to free already-free IRQ 0 [ 190.310861] WARNING: CPU: 2 PID: 1304 at kernel/irq/manage.c:1893 free_irq+0x1b8/0x310
Followed by a backtrace when unbinding the driver. Add an if (client->irq) to bq27xxx_battery_i2c_remove() mirroring probe() to fix this.
From the CVE record · Linux
The Linux kernel’s bq27xxx-i2c driver can try to free IRQ 0 when a device has no IRQ. Unbinding the driver in that condition triggers a kernel warning and backtrace. The input does not describe an attacker path or authentication requirements.
Engineers running Linux kernels with the bq27xxx-i2c driver should check whether their devices lack an IRQ; affected versions are not specified.