power: supply: axp288_fuel_gauge: Fix external_power_changed race
In the Linux kernel, the following vulnerability has been resolved: power: supply: axp288_fuel_gauge: Fix external_power_changed race fuel_gauge_external_power_changed() dereferences info->bat, which gets sets in axp288_fuel_gauge_probe() like this: info->bat = devm_power_supply_register(dev, &fuel_gauge_desc, &psy_cfg); As soon as devm_power_supply_register() has called device_add() the external_power_changed callback can get called. So there is a window where fuel_gauge_external_power_changed() may get called while info->bat has not been set yet leading to a NULL pointer dereference. Fixing this is easy. The external_power_changed callback gets passed the power_supply which will eventually get stored in info->bat, so fuel_gauge_external_power_changed() can simply directly use the passed in psy argument which is always valid.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.31, 6.3.5
- CVEs
- CVE-2023-53310
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 23:11 UTC · Revision 1
Source evidence
power: supply: axp288_fuel_gauge: Fix external_power_changed race
core-osv · Original sourcePublished 16 Sept 2025, 16:11 UTC
In the Linux kernel, the following vulnerability has been resolved: power: supply: axp288_fuel_gauge: Fix external_power_changed race fuel_gauge_external_power_changed() dereferences info->bat, which gets sets in axp288_fuel_gauge_probe() like this: info->bat = devm_power_supply_register(dev, &fuel_gauge_desc, &psy_cfg); As soon as devm_power_supply_register() has called device_add() the external_power_changed callback can get called. So there is a window where fuel_gauge_external_power_changed() may get called while info->bat has not been set yet leading to a NULL pointer dereference. Fixing this is easy. The external_power_changed callback gets passed the power_supply which will eventually get stored in info->bat, so fuel_gauge_external_power_changed() can simply directly use the passed in psy argument which is always valid.
osv:CVE-2023-53310
Kernel
Fixed versions: 6.1.31, 6.3.5
Complete source record
{
"id": "57c5d591b8e68bbc1c5152bfb7b9ce457f388e10c84d1e95a8d3b0ec8f5a3b69",
"url": "https://osv.dev/vulnerability/CVE-2023-53310",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "power: supply: axp288_fuel_gauge: Fix external_power_changed race",
"summary": "In the Linux kernel, the following vulnerability has been resolved: power: supply: axp288_fuel_gauge: Fix external_power_changed race fuel_gauge_external_power_changed() dereferences info->bat, which gets sets in axp288_fuel_gauge_probe() like this: info->bat = devm_power_supply_register(dev, &fuel_gauge_desc, &psy_cfg); As soon as devm_power_supply_register() has called device_add() the external_power_changed callback can get called. So there is a window where fuel_gauge_external_power_changed() may get called while info->bat has not been set yet leading to a NULL pointer dereference. Fixing this is easy. The external_power_changed callback gets passed the power_supply which will eventually get stored in info->bat, so fuel_gauge_external_power_changed() can simply directly use the passed in psy argument which is always valid.",
"evidence": "osv:CVE-2023-53310",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.31",
"evidence": "/affected/1/ranges"
},
{
"value": "6.3.5",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "CVE-2023-53310",
"aliases": [
"CVE-2023-53310"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "30abb3d07929137bf72327560e1595508a692c4e"
},
{
"fixed": "0456b912121e45b3ef54abe3135e5dcb541f956c"
},
{
"fixed": "a636c6ba9ce898207f283271cb28511206ab739b"
},
{
"fixed": "f8319774d6f1567d6e7d03653174ab0c82c5c66d"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53310.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.18.0"
},
{
"fixed": "6.1.31"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.3.5"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-53310.json"
}
}
],
"modified": "2026-10-28T02:30:40.410611920Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0456b912121e45b3ef54abe3135e5dcb541f956c",
"https://git.kernel.org/stable/c/a636c6ba9ce898207f283271cb28511206ab739b",
"https://git.kernel.org/stable/c/f8319774d6f1567d6e7d03653174ab0c82c5c66d",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53310.json",
"https://nvd.nist.gov/vuln/detail/CVE-2023-53310",
"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/2023/53xxx/CVE-2023-53310.json"
}
},
"related_cves": [
{
"value": "CVE-2023-53310",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 507891,
"published_at": "2025-09-16T16:11:48.399+00:00"
}