CVE-2026-53324

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-26. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

net: mana: Use pci_name() for debugfs directory naming

Use pci_name(pdev) for the per-device debugfs directory instead of hardcoded "0" for PFs and pci_slot_name(pdev->slot) for VFs. The previous approach had two issues:

  • pci_slot_name() dereferences pdev->slot, which can be NULL for VFs
in environments like generic VFIO passthrough or nested KVM, causing a NULL pointer dereference.
  • Multiple PFs would all use "0", and VFs across different PCI
domains or buses could share the same slot name, leading to -EEXIST errors from debugfs_create_dir().

pci_name(pdev) returns the unique BDF address, is always valid, and is unique across the system.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 26, 2026

Last Modified

July 6, 2026

Advisory Details (3)

Auto-updated Jul 8, 2026
No patch confirmed yet.
generic

net: mana: Use pci_name() for debugfs directory naming - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c116f07ab9d22bb6f355f3cf9e44c1e6a47fe559
generic

net: mana: Use pci_name() for debugfs directory naming - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9211eb97e8f8c28bf9313ab97862d143dbbbef97
generic

net: mana: Use pci_name() for debugfs directory naming - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/34dbd7b819544c99c9d96b400fe4db613f40ac4b

Vendor Advisories for CVE-2026-53324(1)

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

Patch Availability(8)

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 7× in last 7d / 65× 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.

Showing the most recent 100 of 179 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-06 14:51 UTCEG score recompute
  5. 2026-09-06 14:51 UTCVendor advisory
  6. 2026-09-06 14:51 UTCGHSA enrichment
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-04 05:06 UTCEPSS rescore
  9. 2026-09-01 13:54 UTCEPSS rescore
  10. 2026-09-01 04:40 UTCEPSS rescore
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 19:15 UTCEG score recompute
  13. 2026-08-30 19:15 UTCVendor advisory
  14. 2026-08-30 19:14 UTCGHSA enrichment
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:41 UTCEPSS rescore
  17. 2026-08-27 22:53 UTCEG score recompute
  18. 2026-08-27 22:53 UTCVendor advisory
  19. 2026-08-27 22:53 UTCGHSA enrichment
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-24 12:45 UTCEG score recompute
  24. 2026-08-24 12:45 UTCVendor advisory
  25. 2026-08-24 12:45 UTCGHSA enrichment
Show 75 more
  1. 2026-08-23 08:31 UTCVendor advisory
  2. 2026-08-23 08:31 UTCGHSA enrichment
  3. 2026-08-22 09:20 UTCEG score recompute
  4. 2026-08-22 09:20 UTCVendor advisory
  5. 2026-08-22 09:20 UTCGHSA enrichment
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 05:20 UTCEG score recompute
  8. 2026-08-21 05:20 UTCVendor advisory
  9. 2026-08-21 05:20 UTCGHSA enrichment
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-20 06:32 UTCEG score recompute
  12. 2026-08-20 06:32 UTCVendor advisory
  13. 2026-08-20 06:32 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-18 23:30 UTCEG score recompute
  16. 2026-08-18 23:30 UTCVendor advisory
  17. 2026-08-18 23:30 UTCGHSA enrichment
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 17:05 UTCEG score recompute
  20. 2026-08-17 17:05 UTCVendor advisory
  21. 2026-08-17 17:05 UTCGHSA enrichment
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-16 18:17 UTCEG score recompute
  24. 2026-08-16 18:17 UTCVendor advisory
  25. 2026-08-16 18:17 UTCGHSA enrichment
  26. 2026-08-16 14:56 UTCEPSS rescore
  27. 2026-08-16 02:14 UTCEPSS rescore
  28. 2026-08-15 19:08 UTCEG score recompute
  29. 2026-08-15 19:08 UTCVendor advisory
  30. 2026-08-15 19:08 UTCGHSA enrichment
  31. 2026-08-15 01:30 UTCEPSS rescore
  32. 2026-08-14 20:19 UTCEG score recompute
  33. 2026-08-14 20:19 UTCVendor advisory
  34. 2026-08-14 20:19 UTCGHSA enrichment
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-13 21:31 UTCVendor advisory
  37. 2026-08-13 21:31 UTCGHSA enrichment
  38. 2026-08-12 22:39 UTCEG score recompute
  39. 2026-08-12 22:39 UTCVendor advisory
  40. 2026-08-12 22:39 UTCGHSA enrichment
  41. 2026-08-12 13:51 UTCEPSS rescore
  42. 2026-08-11 23:51 UTCEG score recompute
  43. 2026-08-11 23:51 UTCVendor advisory
  44. 2026-08-11 23:51 UTCGHSA enrichment
  45. 2026-08-11 01:03 UTCEG score recompute
  46. 2026-08-11 01:03 UTCVendor advisory
  47. 2026-08-11 01:03 UTCGHSA enrichment
  48. 2026-08-11 00:00 UTCEPSS rescore
  49. 2026-08-10 02:15 UTCEG score recompute
  50. 2026-08-10 02:15 UTCVendor advisory
  51. 2026-08-10 02:15 UTCGHSA enrichment
  52. 2026-08-09 13:46 UTCEPSS rescore
  53. 2026-08-09 03:28 UTCEG score recompute
  54. 2026-08-09 03:28 UTCVendor advisory
  55. 2026-08-09 03:28 UTCGHSA enrichment
  56. 2026-08-08 16:37 UTCEPSS rescore
  57. 2026-08-08 04:40 UTCVendor advisory
  58. 2026-08-08 04:40 UTCGHSA enrichment
  59. 2026-08-07 05:52 UTCEG score recompute
  60. 2026-08-07 05:52 UTCVendor advisory
  61. 2026-08-07 05:52 UTCGHSA enrichment
  62. 2026-08-06 13:47 UTCEPSS rescore
  63. 2026-08-06 07:04 UTCEG score recompute
  64. 2026-08-06 07:04 UTCVendor advisory
  65. 2026-08-06 07:04 UTCGHSA enrichment
  66. 2026-08-05 19:17 UTCEPSS rescore
  67. 2026-08-05 08:16 UTCEG score recompute
  68. 2026-08-05 08:16 UTCGHSA enrichment
  69. 2026-08-04 15:10 UTCEPSS rescore
  70. 2026-08-04 08:49 UTCEG score recompute
  71. 2026-08-04 08:49 UTCVendor advisory
  72. 2026-08-04 08:49 UTCGHSA enrichment
  73. 2026-08-03 10:36 UTCEPSS rescore
  74. 2026-08-03 08:41 UTCVendor advisory
  75. 2026-08-03 08:41 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53324?
CVE-2026-53324 is a medium vulnerability published on June 26, 2026. In the Linux kernel, the following vulnerability has been resolved: net: mana: Use pci_name() for debugfs directory naming Use pci_name(pdev) for the per-device debugfs directory instead of hardcoded "0" for PFs and pcislotname(pdev->slot) for VFs. The previous approach had two issues: 1.…
When was CVE-2026-53324 disclosed?
CVE-2026-53324 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53324 actively exploited?
CVE-2026-53324 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 98.3% of all scored CVEs.
What is the CVSS score of CVE-2026-53324?
CVE-2026-53324 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53324?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53324, 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-53324

Explore →

Is Your Infrastructure Affected by CVE-2026-53324?

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