CVE-2026-53270

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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:

ipvs: clear the svc scheduler ptr early on edit

ip_vs_edit_service() while unbinding the old scheduler clears the svc->scheduler ptr after the scheduler module initiates RCU callbacks. This can cause packets to use the old scheduler at the time when svc->sched_data is already freed after RCU grace period.

Fix it by clearing the ptr early in ip_vs_unbind_scheduler(), before the done_service method schedules any RCU callbacks.

Also, if the new scheduler fails to initialize when replacing the old scheduler, try to restore the old scheduler while still returning the error code.

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 25, 2026

Last Modified

August 5, 2026

Advisory Details (8)

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

ipvs: clear the svc scheduler ptr early on edit - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipvs: clear the svc scheduler ptr early on edit - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipvs: clear the svc scheduler ptr early on edit - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipvs: clear the svc scheduler ptr early on edit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d4f5004511757e3984901ffb412fcf858d80ed5
generic

ipvs: clear the svc scheduler ptr early on edit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/25918720ba97f974a4f8d433b5a0132c5b43f6f3
generic

ipvs: clear the svc scheduler ptr early on edit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/19a9493faa4bf3c7bd0a386f30b60b1bb4a3da03
generic

ipvs: clear the svc scheduler ptr early on edit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/193989cc6d80dd8e0460fb3992e69fa03bf0ff9b
generic

ipvs: clear the svc scheduler ptr early on edit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/14e4689c113b4c06af1069364ade24fdd7055f33

Vendor Advisories for CVE-2026-53270(2)

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

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-53270?
CVE-2026-53270 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: ipvs: clear the svc scheduler ptr early on edit ipvsedit_service() while unbinding the old scheduler clears the svc->scheduler ptr after the scheduler module initiates RCU callbacks. This can cause packets to use the old scheduler…
When was CVE-2026-53270 disclosed?
CVE-2026-53270 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53270 actively exploited?
CVE-2026-53270 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.8% of all scored CVEs.
What is the CVSS score of CVE-2026-53270?
CVE-2026-53270 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53270?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53270, 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-53270

Explore →

Is Your Infrastructure Affected by CVE-2026-53270?

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