CVE-2026-53000

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released 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:

netfilter: nat: use kfree_rcu to release ops

Florian Westphal says:

"Historically this is not an issue, even for normal base hooks: the data path doesn't use the original nf_hook_ops that are used to register the callbacks.

However, in v5.14 I added the ability to dump the active netfilter hooks from userspace.

This code will peek back into the nf_hook_ops that are available at the tail of the pointer-array blob used by the datapath.

The nat hooks are special, because they are called indirectly from the central nat dispatcher hook. They are currently invisible to the nfnl hook dump subsystem though.

But once that changes the nat ops structures have to be deferred too."

Update nf_nat_register_fn() to deal with partial exposition of the hooks from error path which can be also an issue for nfnetlink_hook.

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

Published

June 24, 2026

Last Modified

August 17, 2026

Advisory Details (3)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

netfilter: nat: use kfree_rcu to release ops - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6eda0d771f94267f73f57c94630aa47e90957915
generic

netfilter: nat: use kfree_rcu to release ops - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3c7511f38ab511b791196b13ae48bf4973bf7dfd
generic

netfilter: nat: use kfree_rcu to release ops - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/32fdd2e38e7435a368d88f5977a7d6585ebc8b0e

Patch Availability(7)

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 ... 7.2~rc5-1~exp1 (335 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc5-1~exp1 (160 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (137 versions)7.0.10-1

Weakness Classification(1)

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

Additional Vendor Advisories

(6)

Data Freshness Timeline

(refreshed 40× in last 7d / 144× 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 216 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53000?
CVE-2026-53000 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: netfilter: nat: use kfree_rcu to release ops Florian Westphal says: "Historically this is not an issue, even for normal base hooks: the data path doesn't use the original nfhookops that are used to register the callbacks. However,…
When was CVE-2026-53000 disclosed?
CVE-2026-53000 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53000 actively exploited?
CVE-2026-53000 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 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-53000?
CVE-2026-53000 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53000?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53000, 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-53000

Explore →

Is Your Infrastructure Affected by CVE-2026-53000?

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