GHSA-VF7G-HG9J-7W2W
Vulnerability from github – Published: 2026-05-28 12:30 – Updated: 2026-05-30 12:30In the Linux kernel, the following vulnerability has been resolved:
scsi: mpt3sas: Limit NVMe request size to 2 MiB
The HBA firmware reports NVMe MDTS values based on the underlying drive capability. However, because the driver allocates a fixed 4K buffer for the PRP list, accommodating at most 512 entries, the driver supports a maximum I/O transfer size of 2 MiB.
Limit max_hw_sectors to the smaller of the reported MDTS and the 2 MiB driver limit to prevent issuing oversized I/O that may lead to a kernel oops.
{
"affected": [],
"aliases": [
"CVE-2026-46105"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-05-28T10:16:25Z",
"severity": "HIGH"
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: mpt3sas: Limit NVMe request size to 2 MiB\n\nThe HBA firmware reports NVMe MDTS values based on the underlying drive\ncapability. However, because the driver allocates a fixed 4K buffer for\nthe PRP list, accommodating at most 512 entries, the driver supports a\nmaximum I/O transfer size of 2 MiB.\n\nLimit max_hw_sectors to the smaller of the reported MDTS and the 2 MiB\ndriver limit to prevent issuing oversized I/O that may lead to a kernel\noops.",
"id": "GHSA-vf7g-hg9j-7w2w",
"modified": "2026-05-30T12:30:24Z",
"published": "2026-05-28T12:30:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-46105"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/04631f55afc543d5431a2bdee7f6cc0f2c0debe7"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/45dcc815fc5539e88154315f36cbcb11d3a52fc2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e5f9824817c6358b9f9738bdb92dec9e4e794d3c"
}
],
"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.
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.