Threats Tagged 'cve-2026-45879'
View all threats tagged with 'cve-2026-45879'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-45879'
Click on any threat for detailed analysis and mitigation recommendations
0 A use-after-free vulnerability exists in the Linux kernel power supply driver for bq25980. The issue arises from requesting an IRQ before registering the power_supply handle, causing a race condition during removal where an interrupt may trigger after the handle is freed but before the IRQ handler is unregistered. This can lead to system crashes or memory corruption. A similar race can occur during probe if an interrupt fires before the power_supply handle is initialized. The fix involves ensuring the IRQ is requested only after the power_supply handle registration. Join the discussion | GCVE Database | 05/27/2026, 15:33:14 UTC Added: 06/26/2026, 22:06:39 UTC |
In the Linux kernel, the following vulnerability has been resolved: power: supply: bq25980: Fix use-after-free in power_supply_changed() Using the `devm_` variant for requesting IRQ _before_ the `devm_` variant for allocating/registering the `power_supply` handle, means that the `power_supply` handle will be deallocated/unregistered _before_ the interrupt handler (since `devm_` naturally deallocates in reverse allocation order). This means that during removal, there is a race condition where an interrupt can fire just _after_ the `power_supply` handle has been freed, *but* just _before_ the corresponding unregistration of the IRQ handler has run. This will lead to the IRQ handler calling `power_supply_changed()` with a freed `power_supply` handle. Which usually crashes the system or otherwise silently corrupts the memory... Note that there is a similar situation which can also happen during `probe()`; the possibility of an interrupt firing _before_ registering the `power_supply` handle. This would then lead to the nasty situation of using the `power_supply` handle *uninitialized* in `power_supply_changed()`. Fix this racy use-after-free by making sure the IRQ is requested _after_ the registration of the `power_supply` handle. Join the discussion | GCVE Database | 05/27/2026, 14:17:00 UTC Added: 07/18/2026, 11:19:17 UTC |
Showing 1 to 2 of 2 results