GHSA-MP22-M63X-2WQ5
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32In the Linux kernel, the following vulnerability has been resolved:
dm: limit target bio polling to one shot
dm_poll_bio() is the ->poll_bio() callback for a stacked dm device. The caller only knows about the dm queue, so it may decide to do a spinning poll if it thinks a single queue is being polled. Passing those flags unchanged to the mapped clone lets blk_mq_poll() spin on a target queue from inside dm_poll_bio().
With io_uring IOPOLL on a dm-stripe target this can keep a task in
dm_poll_bio() -> bio_poll() -> blk_mq_poll()
long enough to trigger an RCU CPU stall, before io_uring gets back to io_iopoll_check() and its need_resched() check.
Keep dm's ->poll_bio() bounded by forcing one-shot polling for target bios. The caller can invoke dm_poll_bio() again if it wants to keep polling, and it also gets a chance to reap completions or reschedule between passes.
{
"affected": [],
"aliases": [
"CVE-2026-74392"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:22:41Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndm: limit target bio polling to one shot\n\ndm_poll_bio() is the -\u003epoll_bio() callback for a stacked dm device.\nThe caller only knows about the dm queue, so it may decide to do a\nspinning poll if it thinks a single queue is being polled. Passing those\nflags unchanged to the mapped clone lets blk_mq_poll() spin on a target\nqueue from inside dm_poll_bio().\n\nWith io_uring IOPOLL on a dm-stripe target this can keep a task in\n\n dm_poll_bio() -\u003e bio_poll() -\u003e blk_mq_poll()\n\nlong enough to trigger an RCU CPU stall, before io_uring gets back to\nio_iopoll_check() and its need_resched() check.\n\nKeep dm\u0027s -\u003epoll_bio() bounded by forcing one-shot polling for target\nbios. The caller can invoke dm_poll_bio() again if it wants to keep\npolling, and it also gets a chance to reap completions or reschedule\nbetween passes.",
"id": "GHSA-mp22-m63x-2wq5",
"modified": "2026-08-15T06:32:32Z",
"published": "2026-08-15T06:32:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74392"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5aa0f9231cbacade065cedd8e9b5ebd067231171"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/6c4ede3b771adbb3bf21ad4e8b8f2f6f6120c4f7"
}
],
"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.