CVE-2024-27412

power: supply: bq27xxx-i2c: Do not free non existing IRQ

MEDIUM

5.5

CVSS Score

Published: May 17, 2024 at 11:50 AM UTC

Updated: June 17, 2026 at 07:19 AM UTC

2 products affected across 2 vendorsLinux KernelDebian Linux

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Debian Linux · Debiandrupal

95%

10.0

Linux Kernel · Linux

95%

v ≥ 4.14.316v ≥ 6.3.54.14.316 ≤ v < 4.154.19.284 ≤ v < 4.19.3095.10.181 ≤ v < 5.10.2125.15.114 ≤ v < 5.15.1515.4.244 ≤ v < 5.4.2716.1.31 ≤ v < 6.1.816.3.5 ≤ v < 6.46.4 ≤ v < 6.6.216.4 ≤ v < 6.7.96.4 ≤ v < 6.86.4.1 ≤ v < 6.6.216.7 ≤ v < 6.7.91da9a4b55a6688e3a30c16d0cf2e7c6a90a684fb28960625adaaf3fa3d83c8d3596661d2576d0a834.14.316 4.19.284444ff00734f3878cd54ddd1ed5e2e6dbea9326d55.10.181 5.15.114 5.4.244 6.1.31 6.3.5 6.4 6.4 rc4 6.4 rc5 6.4 rc6 6.4 rc7 6.8 rc1 6.8 rc2 6.8 rc3 6.8 rc4 6.8 rc5 6.8 rc676d2ed844def0cb8704d766924b07b2a918b3e30ca4a2ddd2e69ca82ca5992d4c49649b2cbac3b74dafe9136be7b7fc30f1f3ca410c15b7cc65bee44e01820a94aea99296e500f54b3f36a2985061045e65fee45687fa2109e03056a696dc7d68a151296

Vendor states this is fixed in 083686474e7c97b0f8b66df37fcb64e432e8b771 (fixed)

Vendor states this is fixed in 2df70149e73e79783bcbc7db4fa51ecef0e2022c (fixed)

Vendor states this is fixed in 7394abc8926adee6a817bab10797e0adc898af77 (fixed)

Vendor states this is fixed in cefe18e9ec84f8fe3e198ccebb815cc996eb9797 (fixed)

Vendor states this is fixed in d4d813c0a14d6bf52d810a55db06a2e7e3d98eaa (fixed)

Vendor states this is fixed in d7acc4a569f5f4513120c85ea2b9f04909b7490f (fixed)

Vendor states this is fixed in e601ae81910ce6a3797876e190a2d8ef6cf828bc (fixed)

Vendor states this is fixed in fbca8bae1ba79d443a58781b45e92a73a24ac8f8 (fixed)

Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 4.19.309 (unaffected)

Vendor states this is fixed in 5.10.212 (unaffected)

Vendor states this is fixed in 5.15.151 (unaffected)

Vendor states this is fixed in 5.4.271 (unaffected)

Vendor states this is fixed in 6.1.81 (unaffected)

Vendor states this is fixed in 6.4 (unaffected)

Vendor states this is fixed in 6.6.21 (unaffected)

Vendor states this is fixed in 6.7.9 (unaffected)

Vendor states this is fixed in 6.8 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references