GHSA-J436-5FX7-7XPM
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
spi: davinci: switch to managed controller allocation
The controller is allocated with the non-managed spi_alloc_host() while the interrupt is registered with devm_request_threaded_irq(). During removal, spi_bitbang_stop() only unregisters the controller; the subsequent spi_controller_put() then frees the controller together with its embedded davinci_spi devdata, which is the IRQ handler's dev_id. The devm_request_threaded_irq() release action (free_irq()), which drains the handler, does not run until after .remove() returns. A late or latched interrupt can therefore reach davinci_spi_irq() and dereference already-freed memory.
Switch to devm_spi_alloc_host() so that the devres LIFO order releases the controller only after free_irq() has drained the handler, and drop the now-redundant spi_controller_put() from .remove(). The probe error path is simplified to direct returns.
The clock is acquired with devm_clk_get_enabled(), which is registered after the IRQ and thus released before it by the devres LIFO order. Drain the interrupt explicitly with devm_free_irq() before disabling the controller so that a late interrupt cannot access the registers of a clock-gated controller.
This issue was found by an in-house static analysis tool.
{
"affected": [],
"aliases": [
"CVE-2026-90410"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:40Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nspi: davinci: switch to managed controller allocation\n\nThe controller is allocated with the non-managed spi_alloc_host() while\nthe interrupt is registered with devm_request_threaded_irq(). During\nremoval, spi_bitbang_stop() only unregisters the controller; the\nsubsequent spi_controller_put() then frees the controller together with\nits embedded davinci_spi devdata, which is the IRQ handler\u0027s dev_id.\nThe devm_request_threaded_irq() release action (free_irq()), which\ndrains the handler, does not run until after .remove() returns. A late\nor latched interrupt can therefore reach davinci_spi_irq() and\ndereference already-freed memory.\n\nSwitch to devm_spi_alloc_host() so that the devres LIFO order releases\nthe controller only after free_irq() has drained the handler, and drop\nthe now-redundant spi_controller_put() from .remove(). The probe error\npath is simplified to direct returns.\n\nThe clock is acquired with devm_clk_get_enabled(), which is registered\nafter the IRQ and thus released before it by the devres LIFO order.\nDrain the interrupt explicitly with devm_free_irq() before disabling the\ncontroller so that a late interrupt cannot access the registers of a\nclock-gated controller.\n\nThis issue was found by an in-house static analysis tool.",
"id": "GHSA-j436-5fx7-7xpm",
"modified": "2026-09-17T18:32:04Z",
"published": "2026-09-17T18:32:04Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90410"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/1a7958ce58dc95b06615df00c120ece4eb9ccc86"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/29e37f768f35592e26477f703649bd2e6f18d857"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3b544072185c3d19ddec621ec9f6897ea2d10ee3"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ea408a05dc8f18b4a184b88d6e19d2fd1acc1527"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f9452eba71fbfcee55c0b8e030ee3615e9f75f65"
}
],
"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.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.