LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel driver memory-safety flaw in qla2xxx. Firmware-reported frame size could cause copying beyond a 64-byte structure member. The source describes a fix, but provides no CVSS score, CWE, or evidence of exploitation.

Executive priority

Treat as a focused kernel maintenance issue for systems using qla2xxx storage drivers. Prioritize patch planning where Fibre Channel storage hosts are exposed, but current sources do not support emergency handling based on exploitation.

Technical view

qla27xx_copy_fpin_pkt() and qla27xx_copy_multiple_pkt() used firmware frame_size to calculate memcpy length into purex_item.iocb, a fixed 64-byte array. Oversized frame_size values could create cross-member writes. The resolved fix caps total_bytes to the iocb member size before allocation and copying.

Likely exposure

Exposure is most likely on affected Linux kernels using the qla2xxx SCSI/Fibre Channel driver path. The source bundle lists Linux as affected and references stable kernel fixes, but does not provide distribution package status or hardware deployment scope.

Exploitation context

The bundle states KEV is false and provides no cited evidence of active exploitation. It describes a firmware-reported size leading to an unsafe kernel memory write, but does not establish practical exploitability or attacker prerequisites.

Researcher notes

Key uncertainty is exploitability. The issue is a bounded destination-member overflow triggered by firmware-reported frame_size, fixed by limiting copy size to sizeof(item->iocb). No CVSS, CWE, distribution impact, or exploit evidence is included in the provided bundle.

Mitigation direction

  • Update to a vendor or stable Linux kernel containing the referenced qla2xxx fixes.
  • Prioritize systems that use qla2xxx for storage connectivity.
  • Check Linux distribution advisories for backported package names and maintenance guidance.
  • Avoid assuming mitigation beyond vendor guidance if a patched kernel is unavailable.

Validation and detection

  • Inventory affected Linux kernel versions against vendor package advisories.
  • Confirm whether qla2xxx is built, loaded, or required on each system.
  • Verify the kernel source or changelog includes one referenced stable fix.
  • Confirm patched code caps total_bytes to 64 bytes before copying.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23059 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux875386b98857822b77ac7f95bdf367b70af5b78c, 875386b98857822b77ac7f95bdf367b70af5b78c, 875386b98857822b77ac7f95bdf367b70af5b78c, 875386b98857822b77ac7f95bdf367b70af5b78cunaffected
LinuxLinux6.6, 0, 6.6.122, 6.12.68, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.