power: supply: sbs-battery: Fix use-after-free in power_supply_changed()
In the Linux kernel, the following vulnerability has been resolved: power: supply: sbs-battery: 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. Keep the old behavior of just printing a warning in case of any failures during the IRQ request and finishing the probe successfully.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.252, 5.15.202, 6.1.165, 6.12.75, 6.18.14, 6.19.4, 6.6.128
- CVEs
- CVE-2026-45916
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 6 Nov 2026, 18:11 UTC · Revision 1
Source evidence
power: supply: sbs-battery: Fix use-after-free in power_supply_changed()
core-osv · Original sourcePublished 27 May 2026, 12:17 UTC
In the Linux kernel, the following vulnerability has been resolved: power: supply: sbs-battery: 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. Keep the old behavior of just printing a warning in case of any failures during the IRQ request and finishing the probe successfully.
osv:CVE-2026-45916
Kernel
Fixed versions: 5.10.252, 5.15.202, 6.1.165, 6.6.128, 6.12.75, 6.18.14, 6.19.4
Complete source record
{
"id": "f506a2fe84885bb8fbc820a8d2a31b931eea49bb52c013b2408721c33ea09deb",
"url": "https://osv.dev/vulnerability/CVE-2026-45916",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "power: supply: sbs-battery: Fix use-after-free in power_supply_changed()",
"summary": "In the Linux kernel, the following vulnerability has been resolved: power: supply: sbs-battery: 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. Keep the old behavior of just printing a warning in case of any failures during the IRQ request and finishing the probe successfully.",
"evidence": "osv:CVE-2026-45916",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.252",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.202",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.165",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.128",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.75",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.14",
"evidence": "/affected/1/ranges"
},
{
"value": "6.19.4",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-45916",
"aliases": [
"CVE-2026-45916"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "d2cec82c28802da31596b395ad292cb8f132fd63"
},
{
"fixed": "ca7dd71773e4e050b0fb98768b7eae60f8d1f38b"
},
{
"fixed": "f1f472b14ad56104ba228b8fbec60d5b21829913"
},
{
"fixed": "8010b745b436c3e1ca5dd960aa29fa3e0f6d8841"
},
{
"fixed": "2078830c32d1e49ac942c6f8c21f35c806ae5e94"
},
{
"fixed": "82d3eb97a976c9d56bb92b241397610e57a9c629"
},
{
"fixed": "861dda7a9074c0ff67788928165ae39d7f647491"
},
{
"fixed": "14d4dee5d8fb361bfff275832087254beab66d72"
},
{
"fixed": "8d59cf3887fbabacef53bfba473e33e8a8d9d07b"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-45916.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.9.0"
},
{
"fixed": "5.10.252"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.202"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.165"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.128"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.75"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.14"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "6.19.4"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-45916.json"
}
}
],
"modified": "2026-10-28T02:30:47.834083254Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/14d4dee5d8fb361bfff275832087254beab66d72",
"https://git.kernel.org/stable/c/2078830c32d1e49ac942c6f8c21f35c806ae5e94",
"https://git.kernel.org/stable/c/8010b745b436c3e1ca5dd960aa29fa3e0f6d8841",
"https://git.kernel.org/stable/c/82d3eb97a976c9d56bb92b241397610e57a9c629",
"https://git.kernel.org/stable/c/861dda7a9074c0ff67788928165ae39d7f647491",
"https://git.kernel.org/stable/c/8d59cf3887fbabacef53bfba473e33e8a8d9d07b",
"https://git.kernel.org/stable/c/ca7dd71773e4e050b0fb98768b7eae60f8d1f38b",
"https://git.kernel.org/stable/c/f1f472b14ad56104ba228b8fbec60d5b21829913",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/45xxx/CVE-2026-45916.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-45916",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/45xxx/CVE-2026-45916.json"
}
},
"related_cves": [
{
"value": "CVE-2026-45916",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 515854,
"published_at": "2026-05-27T12:17:32.565+00:00"
}