Live › vulnerability › CVE-2026-98486
Go to dashboardThe Amazon ENA network driver in the Linux kernel does not free a coherent DMA buffer used for MMIO register reads when device probe fails partway through. The leak is a resource exhaustion issue found by code inspection, and the sources describe no code execution or data exposure.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Hosts that load the Amazon ENA network driver, typically AWS EC2 instances using Elastic Network Adapters, are the ones where the driver code runs. The leak only occurs when probe fails after device init, so systems that probe successfully are not exposed to growing leaks from it. Systems without the ENA driver loaded can skip it.
No product ranges from the sources yet.
uname -r and compare it against the fixed kernel builds in the upstream stable tree or distribution advisorieslsmod | grep enaEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
net: ena: fix MMIO read buffer leak on probe failure
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98486")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.