GHSA-H84P-58MJ-WQ53
Vulnerability from github – Published: 2026-09-17 18:31 – Updated: 2026-09-17 18:31In the Linux kernel, the following vulnerability has been resolved:
block: mtip32xx: synchronize ioctls with device removal
The ioctl handlers only test REMOVE_PENDING before entering mtip_hw_ioctl(). Removal can set that bit immediately afterwards and free dd->port in mtip_hw_exit() while an ioctl still dereferences it. An already open block device can reach the handlers while del_gendisk() is in progress.
Serialize both native and compat ioctls with removal. Set REMOVE_PENDING before taking the mutex so new callers fail after an in-flight ioctl has drained, and hold the mutex until the port has been torn down.
{
"affected": [],
"aliases": [
"CVE-2026-90180"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:12Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nblock: mtip32xx: synchronize ioctls with device removal\n\nThe ioctl handlers only test REMOVE_PENDING before entering\nmtip_hw_ioctl(). Removal can set that bit immediately afterwards and free\ndd-\u003eport in mtip_hw_exit() while an ioctl still dereferences it. An already\nopen block device can reach the handlers while del_gendisk() is in\nprogress.\n\nSerialize both native and compat ioctls with removal. Set REMOVE_PENDING\nbefore taking the mutex so new callers fail after an in-flight ioctl has\ndrained, and hold the mutex until the port has been torn down.",
"id": "GHSA-h84p-58mj-wq53",
"modified": "2026-09-17T18:31:54Z",
"published": "2026-09-17T18:31:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90180"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4609e0e0be709e974bec9b52c5022136d25e97d3"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/521afbd936ac256b7531470b0b9aa96abf9cd853"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/68940f841d013192086a0f6d7cfbac2cd079e228"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8283049aa5fcb4e84b2b2928b2888903bb8ee12e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8a7799597bd683b6bc251fe2edfa9fd1db568a3a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b389dc35a55713ac24a145741e76196fea1663bc"
}
],
"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.