CVE-2026-53234

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

net: ibm: emac: Fix use-after-free during device removal

The driver was using devm_register_netdev() which causes unregister_netdev() to be deferred until the devres cleanup phase, which runs after emac_remove() returns. This creates a use-after-free window where:

  • emac_remove() is called, which tears down hardware (cancels work, detaches
modules, unregisters from MAL)
  • emac_remove() returns
  • devres cleanup runs and finally calls unregister_netdev()

During step 3, the network stack might still process packets, triggering emac_irq(), emac_poll(), or other handlers that access now-freed hardware resources (dev->emacp, dev->mal, etc.).

Fix this by replacing devm_register_netdev() with manual register_netdev() and calling unregister_netdev() at the beginning of emac_remove(), before any hardware teardown. This ensures the network device is fully stopped and unregistered before hardware resources are released.

The change is safe because:

  • dev->ndev is assigned very early in probe (before any error paths that
could bypass emac_remove)
  • platform_set_drvdata() is only called after successful registration, so
emac_remove() only runs for fully registered devices
  • unregister_netdev() is idempotent and safe to call on any registered device

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 8, 2026

Advisory Details (4)

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

net: ibm: emac: Fix use-after-free during device removal - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: ibm: emac: Fix use-after-free during device removal - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: ibm: emac: Fix use-after-free during device removal - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: ibm: emac: Fix use-after-free during device removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a0130d682222ae21afc395aead7cd2d87e1a8358

Vendor Advisories for CVE-2026-53234(1)

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

Affected Packages

(2 across 2 ecosystems)
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 (145 versions)7.0.13-1

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-53234?
CVE-2026-53234 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net: ibm: emac: Fix use-after-free during device removal The driver was using devmregisternetdev() which causes unregister_netdev() to be deferred until the devres cleanup phase, which runs after emac_remove() returns. This creates…
When was CVE-2026-53234 disclosed?
CVE-2026-53234 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53234 actively exploited?
CVE-2026-53234 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 92.5% of all scored CVEs.
What is the CVSS score of CVE-2026-53234?
CVE-2026-53234 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53234?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53234, 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-53234

Explore →

Is Your Infrastructure Affected by CVE-2026-53234?

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