GHSA-M5GJ-J8CW-F6G4
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
scsi: ufs: core: Validate string descriptors
The string descriptor length includes a two-byte header while the UTF-16 payload starts after it. utf16s_to_utf8s() expects a count of UTF-16 code units, not bytes. Passing the payload byte count can make it read beyond the descriptor buffer.
Validate that the payload has an even byte count, pass a code-unit count to the converter, and allocate sufficient UTF-8 output space.
The raw string buffer starts after the descriptor header but its size is bLength. Copying bLength bytes from that pointer can read beyond the response buffer.
Allocate a zeroed bLength-sized buffer and copy only the UTF-16 payload. This preserves the raw buffer size consumed by the RPMB device-ID ABI while avoiding the overread.
{
"affected": [],
"aliases": [
"CVE-2026-92480"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:50Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: ufs: core: Validate string descriptors\n\nThe string descriptor length includes a two-byte header while the UTF-16\npayload starts after it. utf16s_to_utf8s() expects a count of UTF-16 code\nunits, not bytes. Passing the payload byte count can make it read beyond\nthe descriptor buffer.\n\nValidate that the payload has an even byte count, pass a code-unit count to\nthe converter, and allocate sufficient UTF-8 output space.\n\nThe raw string buffer starts after the descriptor header but its size is\nbLength. Copying bLength bytes from that pointer can read beyond the\nresponse buffer.\n\nAllocate a zeroed bLength-sized buffer and copy only the UTF-16\npayload. This preserves the raw buffer size consumed by the RPMB device-ID\nABI while avoiding the overread.",
"id": "GHSA-m5gj-j8cw-f6g4",
"modified": "2026-09-17T18:32:06Z",
"published": "2026-09-17T18:32:06Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-92480"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/66da25277256b6bf4c3fdbf3c9bfd43324c9cf25"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d96e83d028d7d8762e424e49c671d49ac2ecf14f"
}
],
"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.