CVE-2026-97506

crypto: ixp4xx - fix buffer chain unwind on allocation failure

N/A
Published: September 24, 2026 at 04:04 PM UTC
Updated: October 3, 2026 at 11:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: crypto: ixp4xx - fix buffer chain unwind on allocation failure chainup_buffers() builds a linked list of buffer descriptors for a scatterlist. If dma_pool_alloc() fails while constructing the list, the current code sets buf to NULL and later dereferences it unconditionally at the end of the function: buf->next = NULL; buf->phys_next = 0; This can lead to a null-pointer dereference on allocation failure. If the failure happens after part of the descriptor chain has already been allocated and DMA-mapped, the partially constructed chain also needs to be released. Fix this by terminating the partially constructed chain on allocation failure and letting the callers unwind it via their existing cleanup paths. Also fix ablk_perform() to preserve the hook pointers before checking for failure, so partially built chains can be freed correctly.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 2.6.27.22v ≥ 2.6.28.10v ≥ 2.6.29.32.6.27.22 ≤ v < 2.6.282.6.28.10 ≤ v < 2.6.292.6.29.3 ≤ v < 2.6.302.6.30 ≤ v < 5.15.2222.6.30 ≤ v < 6.1.1892.6.30 ≤ v < 6.12.1112.6.30 ≤ v < 6.18.532.6.30 ≤ v < 6.6.1582.6.30 ≤ v < 7.20d44dc59b2b434b29aafeae581d06f81efac7c832.6.27.222.6.28.102.6.29.32.6.305a80273150a8a1725fa70418d106eb1f2ee8fd2f68845515c8b11791b547a2838e22c27dfa3115ee82a8becb9c2c52fc5e67057a43aeded1f0731e7b
Vendor states this is fixed in 028a7f4f3d69e551f6bf9f728d547bbf4cfc707d (fixed)
Vendor states this is fixed in 04cb00106ca4d0fa9eca24cadc4eda6036e855c8 (fixed)
Vendor states this is fixed in 25056329384010a8672552b134f609601dc4f80e (fixed)
Vendor states this is fixed in 4918b0bd7d2baafb45d87dca9e322137c96005c2 (fixed)
Vendor states this is fixed in 8c37bc8d6a6f77bf9593fb1bcab6c14c7cf02991 (fixed)
Vendor states this is fixed in d4007867be42d71795b78fa7f8ce7514dda9ca83 (fixed)
Affected range stops below 2.6.28, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.6.29, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 2.6.30 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card