Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 083686474e7c97b0f8b66df37fcb64e432e8b771, 2df70149e73e79783bcbc7db4fa51ecef0e2022c, 4.15.

Low priority for now. Upgrade to Linux Linux 083686474e7c97b0f8b66df37fcb64e432e8b771, 2df70149e73e79783bcbc7db4fa51ecef0e2022c, 4.15 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 17, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 15th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-27412

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • linux linux kernel4.19.284 and later · before 4.19.309
  • linux linux kernel5.4.244 and later · before 5.4.271
  • linux linux kernel5.10.181 and later · before 5.10.212
  • linux linux kernel5.15.114 and later · before 5.15.151
  • linux linux kernel6.1.31 and later · before 6.1.81
  • linux linux kernel4.14.316 and later · before 4.15
  • linux linux kernel6.4.1 and later · before 6.6.21
  • linux linux kernel6.7 and later · before 6.7.9
  • linux linux kernel6.3.5 and later · before 6.4
  • linux linux kernel6.4
  • linux linux kernel6.8

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • ca4a2ddd2e69ca82ca5992d4c49649b2cbac3b74, 28960625adaaf3fa3d83c8d3596661d2576d0a83, 6.4affected
    • 76d2ed844def0cb8704d766924b07b2a918b3e30 and later · before d4d813c0a14d6bf52d810a55db06a2e7e3d98eaaaffected · git
    • dafe9136be7b7fc30f1f3ca410c15b7cc65bee44 and later · before 7394abc8926adee6a817bab10797e0adc898af77affected · git
    • 1da9a4b55a6688e3a30c16d0cf2e7c6a90a684fb and later · before d7acc4a569f5f4513120c85ea2b9f04909b7490faffected · git
    • e01820a94aea99296e500f54b3f36a2985061045 and later · before e601ae81910ce6a3797876e190a2d8ef6cf828bcaffected · git
    • e65fee45687fa2109e03056a696dc7d68a151296 and later · before cefe18e9ec84f8fe3e198ccebb815cc996eb9797affected · git
    • 444ff00734f3878cd54ddd1ed5e2e6dbea9326d5 and later · before fbca8bae1ba79d443a58781b45e92a73a24ac8f8affected · git
    • 444ff00734f3878cd54ddd1ed5e2e6dbea9326d5 and later · before 083686474e7c97b0f8b66df37fcb64e432e8b771affected · git
    • 444ff00734f3878cd54ddd1ed5e2e6dbea9326d5 and later · before 2df70149e73e79783bcbc7db4fa51ecef0e2022caffected · git
    • 4.19.284 and later · before 4.19.309affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.82-16.1.82-1
Debian:13linuxbefore 6.7.9-16.7.9-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-27410May 17, 2024 · wifi: nl80211: reject iftype change with mesh ID change
    22Monitor
  • ← EarlierCVE-2024-27411May 17, 2024 · drm/nouveau: keep DMA buffers required for suspend/resume
    22Monitor
  • Later →CVE-2024-27413May 17, 2024 · efi/capsule-loader: fix incorrect allocation size
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux083686474e7c97b0f8b66df37fcb64e432e8b771Vendor (CNA)
Linux Linux2df70149e73e79783bcbc7db4fa51ecef0e2022cVendor (CNA)
Linux Linux4.15Vendor (CNA)
Linux Linux4.19.309Vendor (CNA)
Linux Linux5.10.212Vendor (CNA)
Linux Linux5.15.151Vendor (CNA)
Linux Linux5.4.271Vendor (CNA)
Linux Linux6.1.81Vendor (CNA)
Linux Linux6.4Vendor (CNA)
Linux Linux7394abc8926adee6a817bab10797e0adc898af77Vendor (CNA)
Linux Linuxcefe18e9ec84f8fe3e198ccebb815cc996eb9797Vendor (CNA)
Linux Linuxd4d813c0a14d6bf52d810a55db06a2e7e3d98eaaVendor (CNA)
Linux Linuxd7acc4a569f5f4513120c85ea2b9f04909b7490fVendor (CNA)
Linux Linuxe601ae81910ce6a3797876e190a2d8ef6cf828bcVendor (CNA)
Linux Linuxfbca8bae1ba79d443a58781b45e92a73a24ac8f8Vendor (CNA)
debian:linux6.1.82-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (9 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records