CVE-2026-97506

What the bug is

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.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/crypto/intel/ixp4xx/ixp4xx_crypto.c

What this is

ARM/INTEL IXP4XX ARM ARCHITECTUREMAINTAINERS section matched on drivers/crypto/intel/ixp4xx/ixp4xx_crypto.c · linux-arm-kernel@lists.infradead.org · Maintained

Check it on the machine

grep -wE 'CONFIG_CRYPTO|CONFIG_CRYPTO_DEV_IXP4XX' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

Show whether Debian builds this, per release

Debian does not build this code in 4 releases. The build rule could not be established for 1 release, so nothing is claimed about those.

• bookworm?
• trixie, forky, sid, bookworm · linux-6.12n

?

not established - no Makefile entry for the affected file

n

not enabled on any flavour - this release does not build the code

Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.

Build switches

CONFIG_CRYPTO, CONFIG_CRYPTO_DEV_IXP4XX

Reads as

all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published

2026-09-24 (24 days ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.16%, higher than 4.9% of all CVEssource

CISA KEV

not listedthe KEV catalogue

Debian urgency

not yet assignedsource

Subsystem

drivers/crypto

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

Introduced	Fixed in	Commit
2.6.30	5.15.222	d4007867be42
2.6.30	6.1.189	4918b0bd7d2b
2.6.30	6.6.158	8c37bc8d6a6f
2.6.30	6.12.111	04cb00106ca4
2.6.30	6.18.53	028a7f4f3d69
2.6.30	7.2	250563293840
2.6.27.22	0	0
2.6.28.10	0	0
2.6.29.3	0	0

Debian advisories