# CVE-2026-90010: scsi: bsg: Cap io_uring sense copy to max_response_len

> A buffer overflow in the Linux kernel SCSI block layer allows attackers to corrupt memory, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-90010, GHSA-jqrf-j7h5-x2p4, UBUNTU-CVE-2026-90010

## What is CVE-2026-90010?

CVE-2026-90010 is a high-severity memory corruption vulnerability in Linux, published on 16 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: bsg: Cap io_uring sense copy to max_response_len

Completion copied scmd->sense_len to the user response buffer without
honoring max_response_len. After a valid sense, the midlayer sets
sense_len to the real length (up to SCSI_SENSE_BUFFERSIZE), so a smaller
user buffer was overrun.

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


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

Apply the vendor's patch.

## Is CVE-2026-90010 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90010 is a high-severity memory corruption vulnerability in Linux, published on 16 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-90010 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-90010/ (Markdown: https://insights.sbomify.com/CVE-2026-90010/index.md)
```

## Sources

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

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