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-53297net: mana: Guard mana_remove against double invocation

Description

In the Linux kernel, the following vulnerability has been resolved: net: mana: Guard mana_remove against double invocation If PM resume fails (e.g., mana_attach() returns an error), mana_probe() calls mana_remove(), which tears down the device and sets gd->gdma_context = NULL and gd->driver_data = NULL. However, a failed resume callback does not automatically unbind the driver. When the device is eventually unbound, mana_remove() is invoked a second time. Without a NULL check, it dereferences gc->dev with gc == NULL, causing a kernel panic. Add an early return if gdma_context or driver_data is NULL so the second invocation is harmless. Move the dev = gc->dev assignment after the guard so it cannot dereference NULL.

Timeline

  1. ID reserved

    By Linux

  2. · 17 days later

    Published

  3. · 4 months 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

CVSS scores of CVE-2026-53297, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 635096a86edb067d55a1e04b4a918f5c6dac0c51 – < f63a6d2e4167703611f5c2602eaa1a23f635430f
    • affected 635096a86edb067d55a1e04b4a918f5c6dac0c51 – < 793bf1f4e469c51d0e39199823da5e1de85a2741
    • affected 635096a86edb067d55a1e04b4a918f5c6dac0c51 – < 8ee85b75a72216c857c39457f6595709c4c9f856
    • affected 635096a86edb067d55a1e04b4a918f5c6dac0c51 – < a1ddfd2c0b7a48e5239fadd2a24cc4bc2cda90e6
    • affected 635096a86edb067d55a1e04b4a918f5c6dac0c51 – < bbe5c3c570645a4ceb120979d3ee203a1583d775
    • affected 635096a86edb067d55a1e04b4a918f5c6dac0c51 – < 50271d7ec95144d26808025b508f463780517d3c
  • Linux · Linux

    • affected 5.16
    • unaffected < 5.16
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.33 – ≤ 6.18.*
    • unaffected 7.0.10 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .