CVE-2025-68741

What it actually does

Memory corruption occurs when kfree() is called on a pre-allocated purex item from a per-adapter pool instead of the proper qla24xx_free_purex_item() in the qla2xxx_process_purls_iocb() error path.

Why it matters to the business

Linux systems with QLogic Fibre Channel adapters risk crashes, instability, or data corruption during storage operations; widespread kernel use and presence in container images amplify operational disruption potential.

How an attack unfolds

An attacker triggers the error handling path in qla2xxx_process_purls_iocb() after a small allocation returns a pooled item via qla24xx_alloc_purex_item(), causing incorrect kfree() and subsequent memory corruption.

How to fix it

Update the Linux kernel to commit 4bccd506a1f1ab01d1f45b2a3effff6bedc73cf9 or later; update affected GitLab Chainguard images to 17.10.0-r2 or newer.

How to confirm the fix worked

Confirm presence of qla24xx_free_purex_item() call in qla2xxx_process_purls_iocb(); verify running kernel contains the fix commit or updated package version.

Typical attack path

1. Send crafted FC/SCSI traffic to reach qla2xxx_process_purls_iocb()
2. Force allocation from the pre-allocated purex pool
3. Induce error condition that executes the buggy kfree path

How to detect it

Inspect kernel logs for oops, warnings, or crashes mentioning qla2xxx and memory free operations around purex item handling.

What your security team should do

• Apply kernel and image updates to fixed versions immediately
• Prioritize systems with QLogic adapters in storage fabrics
• Monitor vendor advisories for backported patches in distributions