CVE-2026-92480: Linux kernel · scsi: ufs: core: Validate string descriptors
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f3480c59f4ce97d831e9d06f5a2b9c20547ed1a4 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:55 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f3480c59f4ce97d831e9d06f5a2b9c20547ed1a4, d96e83d028d7d8762e424e49c671d49ac2ecf14f, 566109f1ee4e389b4effab43b0ce1fdab302e9de +2
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In 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.
References
- git.kernel.org/stable/c/566109f1ee4e389b4effab43b0ce1fdab302e9de (opens in a new tab)
- git.kernel.org/stable/c/02dd1a65dff842d9360a38ebe243dc8f6adbbaf5 (opens in a new tab)
- git.kernel.org/stable/c/f3480c59f4ce97d831e9d06f5a2b9c20547ed1a4 (opens in a new tab)
- git.kernel.org/stable/c/66da25277256b6bf4c3fdbf3c9bfd43324c9cf25 (opens in a new tab)
- git.kernel.org/stable/c/d96e83d028d7d8762e424e49c671d49ac2ecf14f (opens in a new tab)