CVE-2026-53233

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
Trending — 4 sources updated this week
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

A fix is available — apply it.

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

netdev: fix double-free in netdev_nl_bind_rx_doit()

Sashiko flags that genlmsg_reply() always consumes the skb. The error path calls nlmsg_free(rsp) so we can't jump directly to it. Let's not unbind, just propagate the error to the user. This is the typical way of handling genlmsg_reply() failures. They shouldn't happen unless user does something silly like calling the kernel with an already-full rcvbuf.

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
7%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 7, 2026

Advisory Details (4)

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

netdev: fix double-free in netdev_nl_bind_rx_doit() - kernel/git/stable/linux.git - Linux kernel stable tree

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

netdev: fix double-free in netdev_nl_bind_rx_doit() - kernel/git/stable/linux.git - Linux kernel stable tree

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

netdev: fix double-free in netdev_nl_bind_rx_doit() - kernel/git/stable/linux.git - Linux kernel stable tree

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

netdev: fix double-free in netdev_nl_bind_rx_doit() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9b019376cbee10c4f9184d1745fa37d156e36f30

Vendor Advisories for CVE-2026-53233(1)

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

Patch Availability(4)

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

(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.

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 12× in last 7d / 47× 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 214 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53233?
CVE-2026-53233 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: netdev: fix double-free in netdevnlbindrxdoit() Sashiko flags that genlmsg_reply() always consumes the skb. The error path calls nlmsg_free(rsp) so we can't jump directly to it. Let's not unbind, just propagate the error to the…
When was CVE-2026-53233 disclosed?
CVE-2026-53233 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53233 actively exploited?
CVE-2026-53233 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.7% of all scored CVEs.
What is the CVSS score of CVE-2026-53233?
CVE-2026-53233 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53233?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53233, 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-53233

Explore →

Is Your Infrastructure Affected by CVE-2026-53233?

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