GHSA-5GM7-3J8Q-F938
Vulnerability from github – Published: 2025-12-16 15:30 – Updated: 2025-12-16 15:30In the Linux kernel, the following vulnerability has been resolved:
scsi: core: Fix a regression triggered by scsi_host_busy()
Commit 995412e23bb2 ("blk-mq: Replace tags->lock with SRCU for tag iterators") introduced the following regression:
Call trace: __srcu_read_lock+0x30/0x80 (P) blk_mq_tagset_busy_iter+0x44/0x300 scsi_host_busy+0x38/0x70 ufshcd_print_host_state+0x34/0x1bc ufshcd_link_startup.constprop.0+0xe4/0x2e0 ufshcd_init+0x944/0xf80 ufshcd_pltfrm_init+0x504/0x820 ufs_rockchip_probe+0x2c/0x88 platform_probe+0x5c/0xa4 really_probe+0xc0/0x38c __driver_probe_device+0x7c/0x150 driver_probe_device+0x40/0x120 __driver_attach+0xc8/0x1e0 bus_for_each_dev+0x7c/0xdc driver_attach+0x24/0x30 bus_add_driver+0x110/0x230 driver_register+0x68/0x130 __platform_driver_register+0x20/0x2c ufs_rockchip_pltform_init+0x1c/0x28 do_one_initcall+0x60/0x1e0 kernel_init_freeable+0x248/0x2c4 kernel_init+0x20/0x140 ret_from_fork+0x10/0x20
Fix this regression by making scsi_host_busy() check whether the SCSI host tag set has already been initialized. tag_set->ops is set by scsi_mq_setup_tags() just before blk_mq_alloc_tag_set() is called. This fix is based on the assumption that scsi_host_busy() and scsi_mq_setup_tags() calls are serialized. This is the case in the UFS driver.
{
"affected": [],
"aliases": [
"CVE-2025-68224"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-12-16T14:15:55Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: core: Fix a regression triggered by scsi_host_busy()\n\nCommit 995412e23bb2 (\"blk-mq: Replace tags-\u003elock with SRCU for tag\niterators\") introduced the following regression:\n\nCall trace:\n __srcu_read_lock+0x30/0x80 (P)\n blk_mq_tagset_busy_iter+0x44/0x300\n scsi_host_busy+0x38/0x70\n ufshcd_print_host_state+0x34/0x1bc\n ufshcd_link_startup.constprop.0+0xe4/0x2e0\n ufshcd_init+0x944/0xf80\n ufshcd_pltfrm_init+0x504/0x820\n ufs_rockchip_probe+0x2c/0x88\n platform_probe+0x5c/0xa4\n really_probe+0xc0/0x38c\n __driver_probe_device+0x7c/0x150\n driver_probe_device+0x40/0x120\n __driver_attach+0xc8/0x1e0\n bus_for_each_dev+0x7c/0xdc\n driver_attach+0x24/0x30\n bus_add_driver+0x110/0x230\n driver_register+0x68/0x130\n __platform_driver_register+0x20/0x2c\n ufs_rockchip_pltform_init+0x1c/0x28\n do_one_initcall+0x60/0x1e0\n kernel_init_freeable+0x248/0x2c4\n kernel_init+0x20/0x140\n ret_from_fork+0x10/0x20\n\nFix this regression by making scsi_host_busy() check whether the SCSI\nhost tag set has already been initialized. tag_set-\u003eops is set by\nscsi_mq_setup_tags() just before blk_mq_alloc_tag_set() is called. This\nfix is based on the assumption that scsi_host_busy() and\nscsi_mq_setup_tags() calls are serialized. This is the case in the UFS\ndriver.",
"id": "GHSA-5gm7-3j8q-f938",
"modified": "2025-12-16T15:30:46Z",
"published": "2025-12-16T15:30:46Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-68224"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/143257917b836bd5fc434063030fda199e249624"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/47c8b35a1f1d53aac156480cea0a0c5c82919f03"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5d778778b40bcdfd9f8817fea1ec6ebcbec69c0a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/804b5b8e3545445450387ae6891262c421c49304"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a0b7780602b1b196f47e527fec82166a7e67c4d0"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d579f496681c5136d63cb4fbb685511227e73602"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e208fb1660c4a43f06b7b66c3ff22dde84ec3990"
}
],
"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.