GHSA-4PPC-MF9Q-3J92
Vulnerability from github – Published: 2026-08-27 06:31 – Updated: 2026-08-27 06:31In the Linux kernel, the following vulnerability has been resolved:
mmc: atmel-mci: Fix use-after-free in atmci_remove due to race condition
In atmci_probe, &host->bh_work is bound with atmci_work_func, and atmci_interrupt, atmci_timeout_timer and atmci_dma_complete can all queue this work on system_bh_wq.
If we remove the module, atmci_remove makes cleanup and the memory allocated for host with devm_kzalloc() is released after the remove callback returns, while the work mentioned above may still be pending or running. The sequence of operations that may lead to a UAF bug is as follows:
CPU0 CPU1
| atmci_interrupt
| queue_work(system_bh_wq,
| &host->bh_work)
atmci_remove | atmci_cleanup_slot(...) | atmci_writel(host, ATMCI_IDR, ~0UL) | timer_delete_sync(&host->timer) | dma_release_channel(host->dma.chan) | free_irq(platform_get_irq(pdev, 0), host) | | atmci_work_func | // use host // devm resources released after | // remove returns, host is freed | | // use host (use-after-free)
Fix it by canceling the work after all the sources that can schedule it (IRQ handler, timeout timer and DMA completion callback) have been stopped, and before proceeding with the remaining cleanup in atmci_remove.
{
"affected": [],
"aliases": [
"CVE-2026-80556"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-26T15:17:10Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmmc: atmel-mci: Fix use-after-free in atmci_remove due to race condition\n\nIn atmci_probe, \u0026host-\u003ebh_work is bound with atmci_work_func, and\natmci_interrupt, atmci_timeout_timer and atmci_dma_complete can all\nqueue this work on system_bh_wq.\n\nIf we remove the module, atmci_remove makes cleanup and the memory\nallocated for host with devm_kzalloc() is released after the remove\ncallback returns, while the work mentioned above may still be pending\nor running. The sequence of operations that may lead to a UAF bug is\nas follows:\n\nCPU0 CPU1\n\n | atmci_interrupt\n | queue_work(system_bh_wq,\n | \u0026host-\u003ebh_work)\natmci_remove |\natmci_cleanup_slot(...) |\natmci_writel(host, ATMCI_IDR, ~0UL) |\ntimer_delete_sync(\u0026host-\u003etimer) |\ndma_release_channel(host-\u003edma.chan) |\nfree_irq(platform_get_irq(pdev, 0), host) |\n | atmci_work_func\n | // use host\n// devm resources released after |\n// remove returns, host is freed |\n | // use host (use-after-free)\n\nFix it by canceling the work after all the sources that can schedule\nit (IRQ handler, timeout timer and DMA completion callback) have been\nstopped, and before proceeding with the remaining cleanup in\natmci_remove.",
"id": "GHSA-4ppc-mf9q-3j92",
"modified": "2026-08-27T06:31:32Z",
"published": "2026-08-27T06:31:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80556"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/22aecf6c4721727a2f724ca0438bc7d4b609bf3f"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7599a73ff66d195a908f5d88b427933a9fb1c02a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b5060ff2f5460795a3e9f7cdf5052aa42f96ff81"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c125ee35a49a0518521b52b27631eef061b8719a"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
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.