# CVE-2026-92480: scsi: ufs: core: Validate string descriptors

> A buffer overread in the Linux kernel UFS driver allows attackers to read memory or cause a crash via malformed string descriptors.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-102365, BELL-CVE-2026-92480, DEBIAN-CVE-2026-92480, GHSA-m5gj-j8cw-f6g4, UBUNTU-CVE-2026-92480

## What is CVE-2026-92480?

CVE-2026-92480 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-92480?


## How do I fix CVE-2026-92480?

Apply the vendor's patch.

## Is CVE-2026-92480 being exploited?

There is no known exploitation of CVE-2026-92480 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92480 and fix it if it is affected.

What it is: CVE-2026-92480 is a memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92480 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92480/ (Markdown: https://insights.sbomify.com/CVE-2026-92480/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92480
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92480
- OSV: https://osv.dev/vulnerability/CVE-2026-92480

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92480/
Summaries are generated and may contain mistakes; the official description above is the record.