Service interruption via nonexistent IRQ free
Published May 17, 2024 · Updated May 23, 2026
Improper IRQ handling in affected Linux kernel releases allows local users to interrupt service by unbinding a bq27xxx I2C device. bq27xxx_battery_i2c_remove() calls free_irq() unconditionally when client->irq is zero because the probe registered no interrupt. The affected driver must be bound to an I2C client without an IRQ, and unbinding it produces an already-free IRQ warning and kernel backtrace.
Summary
What happened
Improper IRQ handling in affected Linux kernel releases allows local users to interrupt service by unbinding a bq27xxx I2C device. bq27xxx_battery_i2c_remove() calls free_irq() unconditionally when client->irq is zero because the probe registered no interrupt. The affected driver must be bound to an I2C client without an IRQ, and unbinding it produces an already-free IRQ warning and kernel backtrace.
The record
- CVE
- CVE-2024-27412
- Published
- May 17, 2024
- Updated
- May 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 17, 2024CVE publishedPublication date reported by the CVE source.
- May 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da9a4b55a6688e3a30c16d0cf2e7c6a90a684fb <d7acc4a569f5f4513120c85ea2b9f04909b7490f
- Affected versionversion=28960625adaaf3fa3d83c8d3596661d2576d0a83
- Affected versionversion=4.14.316 <4.15
- Affected versionversion=4.19.284 <4.19.309
- Affected versionversion=444ff00734f3878cd54ddd1ed5e2e6dbea9326d5 <083686474e7c97b0f8b66df37fcb64e432e8b771
- Affected versionversion=444ff00734f3878cd54ddd1ed5e2e6dbea9326d5 <2df70149e73e79783bcbc7db4fa51ecef0e2022c
- Affected versionversion=444ff00734f3878cd54ddd1ed5e2e6dbea9326d5 <fbca8bae1ba79d443a58781b45e92a73a24ac8f8
- Affected versionversion=5.10.181 <5.10.212
- Affected versionversion=5.15.114 <5.15.151
- Affected versionversion=5.4.244 <5.4.271
- Affected versionversion=6.1.31 <6.1.81
- Affected versionversion=6.3.5 <6.4
- Affected versionversion=6.4
- Affected versionversion=76d2ed844def0cb8704d766924b07b2a918b3e30 <d4d813c0a14d6bf52d810a55db06a2e7e3d98eaa
- Affected versionversion=ca4a2ddd2e69ca82ca5992d4c49649b2cbac3b74
- Affected versionversion=dafe9136be7b7fc30f1f3ca410c15b7cc65bee44 <7394abc8926adee6a817bab10797e0adc898af77
- Affected versionversion=e01820a94aea99296e500f54b3f36a2985061045 <e601ae81910ce6a3797876e190a2d8ef6cf828bc
- Affected versionversion=e65fee45687fa2109e03056a696dc7d68a151296 <cefe18e9ec84f8fe3e198ccebb815cc996eb9797
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo