Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98486

net: ena: fix MMIO read buffer leak on probe failure

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.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 12 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 1738cd3ed342294360d6a74d4e58800004bff854 – < 9de940a3c5731be5a544f6f366576cc4dc073f7c
    • affected 1738cd3ed342294360d6a74d4e58800004bff854 – < 4b90112826439149dcee20e73d02f25ae0e2a9fb
    • affected 1738cd3ed342294360d6a74d4e58800004bff854 – < 0d31edc7ff1f7f265c11248819dfaf5a8274b209
    • affected 1738cd3ed342294360d6a74d4e58800004bff854 – < a0f5fd7a285f44fa402242f26feddfe1d4a0fc6c
    • affected 1738cd3ed342294360d6a74d4e58800004bff854 – < 7bd3e9a2d0c288e54f51df260d9433163f5fbc1e
    • affected 1738cd3ed342294360d6a74d4e58800004bff854 – < 30ff01b4c7e419bb70f40f01dcd7f6af680808b3
    • affected 1738cd3ed342294360d6a74d4e58800004bff854 – < 47785f9f638b064ce6e32e8e3b6f1ffd83849fc2
    • affected 1738cd3ed342294360d6a74d4e58800004bff854 – < 9476b4468862927297c94c440863cd8ed1e7cc83
  • Linux · Linux

    • affected 4.9
    • unaffected < 4.9
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.55 – ≤ 6.18.*
    • unaffected 7.2.9 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98486 badge
[![CVE-2026-98486](https://cveledger.app/badge/CVE-2026-98486.svg)](https://cveledger.app/cve/CVE-2026-98486)

Record last updated .