GHSA-9PCH-737P-3QC4
Vulnerability from github – Published: 2026-07-24 18:31 – Updated: 2026-07-24 18:31In the Linux kernel, the following vulnerability has been resolved:
regulator: tps65219: fix irq_data.rdev not being assigned
Commit 64a6b577490c ("regulator: tps65219: Remove debugging helper function") removed the tps65219_get_rdev_by_name() helper along with the irq_data.rdev assignment that depended on it. This left irq_data.rdev uninitialized for all IRQs, causing undefined behavior when regulator_notifier_call_chain() is called from the IRQ handler:
Internal error: Oops: 0000000096000004 pc : regulator_notifier_call_chain lr : tps65219_regulator_irq_handler Call trace: regulator_notifier_call_chain tps65219_regulator_irq_handler handle_nested_irq regmap_irq_thread irq_thread_fn irq_thread kthread ret_from_fork
Instead of restoring a dedicated lookup array, restructure the probe function to combine regulator registration with IRQ registration in the same loop. This way the rdev returned by devm_regulator_register() is naturally available for assigning to irq_data.rdev without any auxiliary data structure.
Non-regulator IRQs (SENSOR, TIMEOUT) that don't correspond to any registered regulator are registered with rdev=NULL, and the IRQ handler is protected with a NULL check to avoid crashing.
{
"affected": [],
"aliases": [
"CVE-2026-64230"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-24T16:16:52Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nregulator: tps65219: fix irq_data.rdev not being assigned\n\nCommit 64a6b577490c (\"regulator: tps65219: Remove debugging helper\nfunction\") removed the tps65219_get_rdev_by_name() helper along with\nthe irq_data.rdev assignment that depended on it. This left\nirq_data.rdev uninitialized for all IRQs, causing undefined behavior\nwhen regulator_notifier_call_chain() is called from the IRQ handler:\n\n Internal error: Oops: 0000000096000004\n pc : regulator_notifier_call_chain\n lr : tps65219_regulator_irq_handler\n Call trace:\n regulator_notifier_call_chain\n tps65219_regulator_irq_handler\n handle_nested_irq\n regmap_irq_thread\n irq_thread_fn\n irq_thread\n kthread\n ret_from_fork\n\nInstead of restoring a dedicated lookup array, restructure the probe\nfunction to combine regulator registration with IRQ registration in\nthe same loop. This way the rdev returned by devm_regulator_register()\nis naturally available for assigning to irq_data.rdev without any\nauxiliary data structure.\n\nNon-regulator IRQs (SENSOR, TIMEOUT) that don\u0027t correspond to any\nregistered regulator are registered with rdev=NULL, and the IRQ handler\nis protected with a NULL check to avoid crashing.",
"id": "GHSA-9pch-737p-3qc4",
"modified": "2026-07-24T18:31:28Z",
"published": "2026-07-24T18:31:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-64230"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6827647fd2dcf4e7f355478a42e82f51e0b5344c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b986f88b22a5374191c195c073350bbeb1bb6518"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f9b2d3b703d13df50c630997dfdc25648e96db0d"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.