CVE-2026-92480: scsi: ufs: core: Validate string descriptors
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 02dd1a65dff842d9360a38ebe243dc8f6adbbaf5, 22c076f72ad67d89dab58d9c97a17c33e8130e82, 566109f1ee4e389b4effab43b0ce1fdab302e9de.
Low priority for now. Upgrade to Linux Linux 02dd1a65dff842d9360a38ebe243dc8f6adbbaf5, 22c076f72ad67d89dab58d9c97a17c33e8130e82, 566109f1ee4e389b4effab43b0ce1fdab302e9de or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.4affected
- 4b828fe156a662a4b6135019bf077040340f299b and later · before 22c076f72ad67d89dab58d9c97a17c33e8130e82affected · git
- 4b828fe156a662a4b6135019bf077040340f299b and later · before 566109f1ee4e389b4effab43b0ce1fdab302e9deaffected · git
- 4b828fe156a662a4b6135019bf077040340f299b and later · before 02dd1a65dff842d9360a38ebe243dc8f6adbbaf5affected · git
- 4b828fe156a662a4b6135019bf077040340f299b and later · before f3480c59f4ce97d831e9d06f5a2b9c20547ed1a4affected · git
- 4b828fe156a662a4b6135019bf077040340f299b and later · before 66da25277256b6bf4c3fdbf3c9bfd43324c9cf25affected · git
- 4b828fe156a662a4b6135019bf077040340f299b and later · before d96e83d028d7d8762e424e49c671d49ac2ecf14faffected · git
- before 5.4not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-92478Sep 17, 2026 · scsi: ufs: core: Validate connected lane counts0Monitor
- ← EarlierCVE-2026-92479Sep 17, 2026 · scsi: ufs: Avoid NULL CQE dereference when reporting invalid tags0Monitor
- Later →CVE-2026-92481Sep 17, 2026 · pinctrl: mediatek: free EINT resources on unbind0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 02dd1a65dff842d9360a38ebe243dc8f6adbbaf5 | Vendor (CNA) |
| Linux Linux | 22c076f72ad67d89dab58d9c97a17c33e8130e82 | Vendor (CNA) |
| Linux Linux | 566109f1ee4e389b4effab43b0ce1fdab302e9de | Vendor (CNA) |
| Linux Linux | 66da25277256b6bf4c3fdbf3c9bfd43324c9cf25 | Vendor (CNA) |
| Linux Linux | d96e83d028d7d8762e424e49c671d49ac2ecf14f | Vendor (CNA) |
| Linux Linux | f3480c59f4ce97d831e9d06f5a2b9c20547ed1a4 | Vendor (CNA) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.6-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/22c076f72ad67d89dab58d9c97a17c33e8130e82
- git.kernel.org/stable/c/566109f1ee4e389b4effab43b0ce1fdab302e9de
- git.kernel.org/stable/c/66da25277256b6bf4c3fdbf3c9bfd43324c9cf25
- git.kernel.org/stable/c/d96e83d028d7d8762e424e49c671d49ac2ecf14f
- git.kernel.org/stable/c/f3480c59f4ce97d831e9d06f5a2b9c20547ed1a4
Vendor advisories and official records. Exploit/PoC links are deliberately left out.