CVE-2026-53089

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. 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

A fix is available — apply it.

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

bpf: Fix use-after-free in offloaded map/prog info fill

When querying info for an offloaded BPF map or program, bpf_map_offload_info_fill_ns() and bpf_prog_offload_info_fill_ns() obtain the network namespace with get_net(dev_net(offmap->netdev)). However, the associated netdev's netns may be racing with teardown during netns destruction. If the netns refcount has already reached 0, get_net() performs a refcount_t increment on 0, triggering:

refcount_t: addition on 0; use-after-free.

Although rtnl_lock and bpf_devs_lock ensure the netdev pointer remains valid, they cannot prevent the netns refcount from reaching zero.

Fix this by using maybe_get_net() instead of get_net(). maybe_get_net() uses refcount_inc_not_zero() and returns NULL if the refcount is already zero, which causes ns_get_path_cb() to fail and the caller to return -ENOENT -- the correct behavior when the netns is being destroyed.

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

Published

June 24, 2026

Last Modified

September 2, 2026

Advisory Details (2)

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

bpf: Fix use-after-free in offloaded map/prog info fill - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix use-after-free in offloaded map/prog info fill - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-53089(2)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)6.1.187-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (176 versions)
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 4× in last 7d / 80× 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 217 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 13:47 UTCEPSS rescore
  5. 2026-09-04 05:06 UTCEPSS rescore
  6. 2026-09-02 14:12 UTCEPSS rescore
  7. 2026-09-02 13:36 UTCGHSA enrichment
  8. 2026-09-02 12:56 UTCEG score recompute
  9. 2026-09-02 12:56 UTCGHSA enrichment
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-09-01 04:40 UTCEPSS rescore
  12. 2026-08-30 19:54 UTCEG score recompute
  13. 2026-08-30 19:54 UTCVendor advisory
  14. 2026-08-30 19:54 UTCGHSA enrichment
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-28 03:44 UTCEG score recompute
  17. 2026-08-28 03:44 UTCVendor advisory
  18. 2026-08-28 03:44 UTCGHSA enrichment
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-24 21:54 UTCEG score recompute
  23. 2026-08-24 21:54 UTCVendor advisory
  24. 2026-08-24 21:54 UTCGHSA enrichment
  25. 2026-08-24 04:34 UTCVendor advisory
Show 75 more
  1. 2026-08-24 04:34 UTCGHSA enrichment
  2. 2026-08-23 13:26 UTCVendor advisory
  3. 2026-08-23 13:26 UTCGHSA enrichment
  4. 2026-08-23 00:55 UTCEG score recompute
  5. 2026-08-23 00:55 UTCVendor advisory
  6. 2026-08-23 00:55 UTCGHSA enrichment
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-22 11:32 UTCEG score recompute
  9. 2026-08-22 11:32 UTCVendor advisory
  10. 2026-08-22 11:32 UTCGHSA enrichment
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 21:02 UTCVendor advisory
  13. 2026-08-21 21:02 UTCGHSA enrichment
  14. 2026-08-21 08:30 UTCEG score recompute
  15. 2026-08-21 08:30 UTCVendor advisory
  16. 2026-08-21 08:30 UTCGHSA enrichment
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 19:59 UTCVendor advisory
  19. 2026-08-20 19:59 UTCGHSA enrichment
  20. 2026-08-20 07:19 UTCVendor advisory
  21. 2026-08-20 07:19 UTCGHSA enrichment
  22. 2026-08-19 14:51 UTCVendor advisory
  23. 2026-08-19 14:51 UTCGHSA enrichment
  24. 2026-08-19 02:03 UTCEG score recompute
  25. 2026-08-19 02:03 UTCVendor advisory
  26. 2026-08-19 02:03 UTCGHSA enrichment
  27. 2026-08-18 13:48 UTCEPSS rescore
  28. 2026-08-17 13:47 UTCEPSS rescore
  29. 2026-08-17 05:01 UTCVendor advisory
  30. 2026-08-17 05:01 UTCGHSA enrichment
  31. 2026-08-16 16:30 UTCEG score recompute
  32. 2026-08-16 16:30 UTCVendor advisory
  33. 2026-08-16 16:30 UTCGHSA enrichment
  34. 2026-08-16 14:56 UTCEPSS rescore
  35. 2026-08-16 03:59 UTCEG score recompute
  36. 2026-08-16 03:59 UTCVendor advisory
  37. 2026-08-16 03:59 UTCGHSA enrichment
  38. 2026-08-16 02:14 UTCEPSS rescore
  39. 2026-08-15 15:28 UTCVendor advisory
  40. 2026-08-15 15:28 UTCGHSA enrichment
  41. 2026-08-15 02:57 UTCEG score recompute
  42. 2026-08-15 02:57 UTCVendor advisory
  43. 2026-08-15 02:57 UTCGHSA enrichment
  44. 2026-08-15 01:30 UTCEPSS rescore
  45. 2026-08-14 14:26 UTCVendor advisory
  46. 2026-08-14 14:26 UTCGHSA enrichment
  47. 2026-08-14 01:54 UTCEG score recompute
  48. 2026-08-14 01:54 UTCVendor advisory
  49. 2026-08-14 01:54 UTCGHSA enrichment
  50. 2026-08-13 22:00 UTCEPSS rescore
  51. 2026-08-13 13:23 UTCVendor advisory
  52. 2026-08-13 13:23 UTCGHSA enrichment
  53. 2026-08-13 00:52 UTCEG score recompute
  54. 2026-08-13 00:52 UTCVendor advisory
  55. 2026-08-13 00:52 UTCGHSA enrichment
  56. 2026-08-12 13:51 UTCEPSS rescore
  57. 2026-08-12 12:21 UTCVendor advisory
  58. 2026-08-12 12:21 UTCGHSA enrichment
  59. 2026-08-11 23:36 UTCVendor advisory
  60. 2026-08-11 23:36 UTCGHSA enrichment
  61. 2026-08-11 11:05 UTCEG score recompute
  62. 2026-08-11 11:05 UTCVendor advisory
  63. 2026-08-11 11:05 UTCGHSA enrichment
  64. 2026-08-11 00:00 UTCEPSS rescore
  65. 2026-08-10 22:34 UTCVendor advisory
  66. 2026-08-10 22:34 UTCGHSA enrichment
  67. 2026-08-10 10:02 UTCVendor advisory
  68. 2026-08-10 10:02 UTCGHSA enrichment
  69. 2026-08-09 21:32 UTCEG score recompute
  70. 2026-08-09 21:32 UTCVendor advisory
  71. 2026-08-09 21:32 UTCGHSA enrichment
  72. 2026-08-09 13:46 UTCEPSS rescore
  73. 2026-08-09 09:00 UTCVendor advisory
  74. 2026-08-09 09:00 UTCGHSA enrichment
  75. 2026-08-08 20:29 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-53089?
CVE-2026-53089 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Fix use-after-free in offloaded map/prog info fill When querying info for an offloaded BPF map or program, bpfmapoffloadinfofillns() and bpfprogoffloadinfofillns() obtain the network namespace with…
When was CVE-2026-53089 disclosed?
CVE-2026-53089 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on September 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53089 actively exploited?
CVE-2026-53089 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-53089?
CVE-2026-53089 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53089?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53089, 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-53089

Explore →

Is Your Infrastructure Affected by CVE-2026-53089?

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