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.
Published: 2026-09-24
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Denial of Service via Kernel Crash
Action: Immediate Patch
AI Analysis

Impact

The ixp4xx crypto driver builds a linked list of buffer descriptors for scatterlists through the function chainup_buffers. When dma_pool_alloc fails during this construction, the code sets a buffer pointer to NULL and later dereferences it unconditionally, triggering a null‑pointer dereference. This flaw leads to a kernel crash. Additionally, if the failure occurs after part of the descriptor chain has already been allocated and DMA‑mapped, the partially constructed chain is not released, exacerbating the instability. The weakness is a classic null‑pointer dereference, catalogued as CWE‑476.

Affected Systems

The flaw exists in any Linux kernel that includes the ixp4xx crypto driver before the patch was applied. All distributions shipping such kernels with this driver compiled are potentially affected. No specific version numbers are listed in the advisory, so the safest assumption is that any kernel prior to the patch commit is vulnerable.

Risk and Exploitability

The CVSS score is 5.5 and the EPSS score is < 1%, indicating a low probability of exploitation, and the vulnerability is not listed in the CISA KEV catalog. The known effect is a kernel crash, which is a high‑severity outcome. Based on the description, the likely attack vector is local; an attacker or system component that can force a DMA allocation failure while the ixp4xx driver is active could trigger the crash. No public exploit is documented, but the presence of an unhandled null dereference indicates a moderate to high exploitation complexity.

Generated by OpenCVE AI on October 1, 2026 at 10:24 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply a kernel update that includes the ixp4xx buffer chain unwind fix.
  • If an update is not feasible, disable or unload the ixp4xx crypto driver and avoid using cryptographic services that depend on it.
  • Monitor kernel logs for panics or errors related to the ixp4xx driver and coordinate with the distribution vendor to release a patched kernel.

Generated by OpenCVE AI on October 1, 2026 at 10:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DLA Debian DLA DLA-4817-1 linux-6.12 security update
Debian DSA Debian DSA DSA-6528-1 linux security update
History

Sat, 03 Oct 2026 11:15:00 +0000


Tue, 29 Sep 2026 13:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Fri, 25 Sep 2026 08:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-476

Thu, 24 Sep 2026 16:30:00 +0000

Type Values Removed Values Added
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.
Title crypto: ixp4xx - fix buffer chain unwind on allocation failure
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-03T10:59:03.858Z

Reserved: 2026-09-24T16:01:01.151Z

Link: CVE-2026-97506

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-24T17:17:28.423

Modified: 2026-10-03T11:17:59.963

Link: CVE-2026-97506

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-09-24T00:00:00Z

Links: CVE-2026-97506 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-01T10:30:08Z

Weaknesses