VulnerabilityPublished 28 Oct 2026

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

Source GCVE Database

Authoritative record:CVE-2026-99157

Not known to be exploited · fixed in ec6b083915e8146e147314a5f4f1285d07b57bfc : update Linux kernel when convenient.

Data as of 28 Oct 2026, 14:01 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch: Available – fixed in ec6b083915e8146e147314a5f4f1285d07b57bfc, 7a755f6d47b811d3abd93c1642ce5e63894540b8, 2effbe746452c108188f85a6951f2b0b65653840

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-m9gv-84j2-4jhf

What to do

Upgrade Linux kernel to ec6b083915e8146e147314a5f4f1285d07b57bfc, 7a755f6d47b811d3abd93c1642ce5e63894540b8 or 2effbe746452c108188f85a6951f2b0b65653840.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 6ff265fc5ef660499e0edc4641647e99eed3f519, < ec6b083915e8146e147314a5f4f1285d07b57bfc	Fixed in ec6b083915e8146e147314a5f4f1285d07b57bfc
LinuxLinux	Affected ≥ 6ff265fc5ef660499e0edc4641647e99eed3f519, < 7a755f6d47b811d3abd93c1642ce5e63894540b8	Fixed in 7a755f6d47b811d3abd93c1642ce5e63894540b8
LinuxLinux	Affected ≥ 6ff265fc5ef660499e0edc4641647e99eed3f519, < 2effbe746452c108188f85a6951f2b0b65653840	Fixed in 2effbe746452c108188f85a6951f2b0b65653840
LinuxLinux	Affected =6.3	Fixed in–
Red Hatredhat/kernel`pkg:rpm/redhat/kernel`Other threats	Affected =6.3	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available that modifies the bsg_setup_queue() call to use the correct reply buffer size for UFS ARPMB replies, preventing buffer overflow. Users should apply the updated Linux kernel version containing this fix. No additional mitigation steps are indicated.

Description

A buffer overflow vulnerability in the Linux kernel's SCSI bsg interface was fixed by adjusting the reply buffer size to accommodate larger UFS ARPMB replies. The previous fixed 96-byte buffer was insufficient for the 104-byte ufs_rpmb_reply structure, causing an 8-byte overflow when handling Advanced RPMB commands with Extended Header Segments (EHS).

Impact

The vulnerability could cause an 8-byte buffer overflow in kernel memory when processing certain UFS Advanced RPMB commands, potentially leading to memory corruption. The input data does not specify exploitation details or impact beyond the overflow condition.

Summary

The Linux kernel's bsg-lib allocated a 96-byte reply buffer per job, but the struct ufs_rpmb_reply requires 104 bytes due to a 40-byte header and a 64-byte EHS. This mismatch caused ufshcd_advanced_rpmb_req_handler() to write 8 bytes beyond the allocated buffer when processing Advanced RPMB commands that include an EHS. The fix involves passing the correct reply buffer size to bsg_setup_queue() so that the full ufs_rpmb_reply fits in the buffer, preventing overflow and ensuring the entire reply reaches user space. Other transports continue using the original 96-byte buffer size.

References

Community reviews

Loading reviews…