CVE-2026-53227

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

net: openvswitch: fix possible kfree_skb of ERR_PTR

After the patch in the "Fixes" tag, the allocation of the "reply" skb can happen either before or after locking the ovs_mutex.

However, error cleanups still follow the classical reversed order, assuming "reply" is allocated before locking: it is freed after unlocking.

If "reply" allocation happens after locking the mutex and it fails, "reply" is left with an ERR_PTR, and execution jumps to the correspondent cleanup stage which will try to free an invalid pointer.

Fix this by setting the pointer to NULL after having saved its error value.

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

Published

June 25, 2026

Last Modified

July 2, 2026

Advisory Details (8)

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

net: openvswitch: fix possible kfree_skb of ERR_PTR - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: openvswitch: fix possible kfree_skb of ERR_PTR - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: openvswitch: fix possible kfree_skb of ERR_PTR - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: openvswitch: fix possible kfree_skb of ERR_PTR - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: openvswitch: fix possible kfree_skb of ERR_PTR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/971b1b37774f13acc5add0a2843f8598446b8598
generic

net: openvswitch: fix possible kfree_skb of ERR_PTR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/895d1dd9057cde1687fa0f4286d47ceed0b82997
generic

net: openvswitch: fix possible kfree_skb of ERR_PTR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/25fdf53698535fe8790237f5a8a9626791429785
generic

net: openvswitch: fix possible kfree_skb of ERR_PTR - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0bb5b2dc1b90aa7dd1473fc8c4d813a29255ff8d

Vendor Advisories for CVE-2026-53227(2)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu

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

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

Weakness Classification(1)

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

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 43× 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 209 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53227?
CVE-2026-53227 is a medium vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: fix possible kfreeskb of ERRPTR After the patch in the "Fixes" tag, the allocation of the "reply" skb can happen either before or after locking the ovs_mutex. However, error cleanups still follow the classical…
When was CVE-2026-53227 disclosed?
CVE-2026-53227 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 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-53227 actively exploited?
CVE-2026-53227 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-53227?
CVE-2026-53227 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53227?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53227, 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-53227

Explore →

Is Your Infrastructure Affected by CVE-2026-53227?

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

Start Free Scan →Browse All CVEs