CVE-2026-63973

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net: mana: Add NULL guards in teardown path to prevent panic on attach failure

When queue allocation fails partway through, the error cleanup frees and NULLs apc->tx_qp and apc->rxqs. Multiple teardown paths such as mana_remove(), mana_change_mtu() recovery, and internal error handling in mana_alloc_queues() can subsequently call into functions that dereference these pointers without NULL checks:

  • mana_chn_setxdp() dereferences apc->rxqs[0], causing a NULL pointer
dereference panic (CR2: 0000000000000000 at mana_chn_setxdp+0x26).
  • mana_destroy_vport() iterates apc->rxqs without a NULL check.
  • mana_fence_rqs() iterates apc->rxqs without a NULL check.
  • mana_dealloc_queues() iterates apc->tx_qp without a NULL check.

Add NULL guards for apc->rxqs in mana_fence_rqs(), mana_destroy_vport(), and before the mana_chn_setxdp() call. Add a NULL guard for apc->tx_qp in mana_dealloc_queues() to skip TX queue draining when TX queues were never allocated or already freed.

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 30, 2026

Vendor Advisories for CVE-2026-63973(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 11× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 02:54 UTCVendor advisory
  2. 2026-08-30 02:54 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 22:30 UTCVendor advisory
  7. 2026-08-26 22:30 UTCGHSA enrichment
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 05:36 UTCVendor advisory
  11. 2026-08-24 05:36 UTCGHSA enrichment
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 12:43 UTCVendor advisory
  15. 2026-08-21 12:43 UTCGHSA enrichment
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 19:50 UTCVendor advisory
  19. 2026-08-18 19:50 UTCGHSA enrichment
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-15 21:01 UTCVendor advisory
  24. 2026-08-15 21:01 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 54 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-13 04:08 UTCVendor advisory
  3. 2026-08-13 04:08 UTCGHSA enrichment
  4. 2026-08-12 13:51 UTCEPSS rescore
  5. 2026-08-11 00:00 UTCEPSS rescore
  6. 2026-08-10 11:15 UTCVendor advisory
  7. 2026-08-10 11:15 UTCGHSA enrichment
  8. 2026-08-09 13:47 UTCEPSS rescore
  9. 2026-08-08 16:37 UTCEPSS rescore
  10. 2026-08-07 18:21 UTCVendor advisory
  11. 2026-08-07 18:21 UTCGHSA enrichment
  12. 2026-08-06 13:47 UTCEPSS rescore
  13. 2026-08-05 19:17 UTCEPSS rescore
  14. 2026-08-05 19:17 UTCEPSS rescore
  15. 2026-08-05 01:28 UTCVendor advisory
  16. 2026-08-05 01:28 UTCGHSA enrichment
  17. 2026-08-04 15:10 UTCEPSS rescore
  18. 2026-08-04 10:39 UTCEPSS rescore
  19. 2026-08-03 10:36 UTCEPSS rescore
  20. 2026-08-02 08:35 UTCVendor advisory
  21. 2026-08-02 08:35 UTCGHSA enrichment
  22. 2026-08-02 02:27 UTCEPSS rescore
  23. 2026-08-01 04:16 UTCEPSS rescore
  24. 2026-07-30 16:28 UTCEPSS rescore
  25. 2026-07-30 15:41 UTCEG score recompute
  26. 2026-07-30 15:41 UTCVendor advisory
  27. 2026-07-30 15:41 UTCGHSA enrichment
  28. 2026-07-30 01:30 UTCEPSS rescore
  29. 2026-07-30 01:30 UTCEPSS rescore
  30. 2026-07-29 03:55 UTCGHSA enrichment
  31. 2026-07-28 15:37 UTCEPSS rescore
  32. 2026-07-27 14:14 UTCEPSS rescore
  33. 2026-07-26 14:54 UTCEPSS rescore
  34. 2026-07-26 14:54 UTCEPSS rescore
  35. 2026-07-26 10:58 UTCEG score recompute
  36. 2026-07-26 10:58 UTCVendor advisory
  37. 2026-07-26 10:58 UTCGHSA enrichment
  38. 2026-07-25 14:18 UTCEPSS rescore
  39. 2026-07-25 14:18 UTCEPSS rescore
  40. 2026-07-24 14:18 UTCEPSS rescore
  41. 2026-07-24 14:18 UTCEPSS rescore
  42. 2026-07-23 14:18 UTCEPSS rescore
  43. 2026-07-23 14:18 UTCEPSS rescore
  44. 2026-07-23 03:22 UTCEG score recompute
  45. 2026-07-22 14:08 UTCEPSS rescore
  46. 2026-07-22 14:08 UTCEPSS rescore
  47. 2026-07-21 15:25 UTCEPSS rescore
  48. 2026-07-21 15:25 UTCEPSS rescore
  49. 2026-07-20 17:31 UTCEG score recompute
  50. 2026-07-20 17:31 UTCGHSA enrichment
  51. 2026-07-20 17:08 UTCEPSS rescore
  52. 2026-07-19 17:49 UTCNVD update
  53. 2026-07-19 15:21 UTCEG score recompute
  54. 2026-07-19 15:19 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-63973?
CVE-2026-63973 is a publicly disclosed vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: net: mana: Add NULL guards in teardown path to prevent panic on attach failure When queue allocation fails partway through, the error cleanup frees and NULLs apc->tx_qp and apc->rxqs. Multiple teardown paths such as manaremove(),…
When was CVE-2026-63973 disclosed?
CVE-2026-63973 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63973 actively exploited?
CVE-2026-63973 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.7% of all scored CVEs.
How do I remediate CVE-2026-63973?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63973, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63973

Explore →

Is Your Infrastructure Affected by CVE-2026-63973?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.