# CVE-2026-23059: scsi: qla2xxx: Sanitize payload size to prevent member overflow

> A buffer overflow in the qla2xxx SCSI driver allows attackers with local access or adjacent network position to cause memory corruption, potentially leading to code execution or system crashes.

- **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:** 4 Feb 2026
- **Updated:** 11 May 2026
- **Also known as:** AZL-77244, BELL-CVE-2026-23059, DEBIAN-CVE-2026-23059, GHSA-6mm8-fcwp-3g49, ROOT-OS-DEBIAN-13-CVE-2026-23059, ROOT-OS-UBUNTU-2404-CVE-2026-23059, UBUNTU-CVE-2026-23059

## What is CVE-2026-23059?

CVE-2026-23059 is a memory corruption vulnerability in Linux, published on 4 Feb 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: qla2xxx: Sanitize payload size to prevent member overflow

In qla27xx_copy_fpin_pkt() and qla27xx_copy_multiple_pkt(), the frame_size
reported by firmware is used to calculate the copy length into
item->iocb. However, the iocb member is defined as a fixed-size 64-byte
array within struct purex_item.

If the reported frame_size exceeds 64 bytes, subsequent memcpy calls will
overflow the iocb member boundary. While extra memory might be allocated,
this cross-member write is unsafe and triggers warnings under
CONFIG_FORTIFY_SOURCE.

Fix this by capping total_bytes to the size of the iocb member (64 bytes)
before allocation and copying. This ensures all copies remain within the
bounds of the destination structure member.

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


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

Apply the vendor's patch.

## Is CVE-2026-23059 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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