CVE-2026-98486

What the bug is

ena_device_init() initializes the MMIO read mechanism with ena_com_mmio_reg_read_request_init(), which allocates a coherent DMA buffer for MMIO read responses. The normal removal path releases this buffer through ena_com_mmio_reg_read_request_destroy(). However, if ena_probe() fails after ena_device_init() succeeds, the error path destroys the admin resources and eventually frees ena_dev without destroying the MMIO read request, leaving the coherent DMA buffer allocated. Call ena_com_mmio_reg_read_request_destroy() in the probe error path before releasing the remaining device resources. This issue was found by manual code inspection.

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/net/ethernet/amazon/ena/ena_netdev.c

What this is

AMAZON ETHERNET DRIVERSMAINTAINERS section matched on drivers/net/ethernet/amazon/ · netdev@vger.kernel.org · Maintained

Kernel module

ena

Check it on the machine

grep -wE 'CONFIG_ENA_ETHERNET|CONFIG_ETHERNET|CONFIG_NET_VENDOR_AMAZON' /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.

lsmod | grep -w ena

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.

• bookwormm
• trixieMnot built on armel/rpi, s390x/s390x
• forky, sidMnot built on s390x/s390x

m

a loadable module on every flavour - check lsmod, can be blacklisted

M

a module where it is built at all; some flavours do not build it

Build switches

CONFIG_ENA_ETHERNET, CONFIG_ETHERNET, CONFIG_NET_VENDOR_AMAZON

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-10-18 (today)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

not scored

CISA KEV

not listedthe KEV catalogue

Debian urgency

not yet assignedsource

Subsystem

drivers/net

Upstream fixes

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

Introduced	Fixed in	Commit
4.9	6.12.112	7bd3e9a2d0c2
4.9	6.18.55	30ff01b4c7e4
4.9	7.2.9	47785f9f638b
4.9	7.3	9476b4468862