# CVE-2026-99157: scsi: bsg: Pass reply_len to bsg_setup_queue() to fit UFS ARPMB replies


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** AZL-111299, BELL-CVE-2026-99157, DEBIAN-CVE-2026-99157, GHSA-m9gv-84j2-4jhf, UBUNTU-CVE-2026-99157

## What is CVE-2026-99157?

CVE-2026-99157 is a vulnerability in Linux, published on 28 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

scsi: bsg: Pass reply_len to bsg_setup_queue() to fit UFS ARPMB replies

bsg-lib allocates a 96-byte (SCSI_SENSE_BUFFERSIZE) reply buffer per
job, but struct ufs_rpmb_reply is 104 bytes: a 40-byte struct
ufs_bsg_reply followed by a 64-byte EHS. When an Advanced RPMB command
returns an EHS, ufshcd_advanced_rpmb_req_handler() copies it right after
the 40-byte header and writes 8 bytes past the end of the buffer.

Let each BSG transport pass its reply buffer size to bsg_setup_queue()
and have ufs_bsg request sizeof(struct ufs_rpmb_reply), so the full
reply reaches user space. Other transports keep SCSI_SENSE_BUFFERSIZE.

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


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

Upgrade to a fixed version.

## Is CVE-2026-99157 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-99157 is a vulnerability in Linux, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99157 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-99157/ (Markdown: https://insights.sbomify.com/CVE-2026-99157/index.md)
```

## Sources

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

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