CVE-2026-53227

MEDIUMNVD 5.55.5—
EchelonGraph scoreHIGH 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 — 5 sources updated this week
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 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:

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(high)
EPSS
3.4%
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 34× 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.

  1. 2026-07-06 13:21 UTCEG score recompute
  2. 2026-07-06 13:21 UTCVendor advisory
  3. 2026-07-06 13:21 UTCGHSA enrichment
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 13:43 UTCEG score recompute
  7. 2026-07-05 13:43 UTCVendor advisory
  8. 2026-07-05 13:42 UTCGHSA enrichment
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 14:04 UTCEG score recompute
  12. 2026-07-04 14:04 UTCVendor advisory
  13. 2026-07-04 14:04 UTCGHSA enrichment
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-03 14:26 UTCEG score recompute▲ 5.50
  17. 2026-07-03 14:26 UTCVendor advisory
  18. 2026-07-03 14:26 UTCGHSA enrichment
  19. 2026-07-02 22:05 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-30 21:00 UTCVendor advisory
  23. 2026-06-30 21:00 UTCGHSA enrichment
  24. 2026-06-29 14:06 UTCEPSS rescore
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 9 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-28 03:34 UTCEG score recompute
  5. 2026-06-28 03:33 UTCGHSA enrichment
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-25 13:49 UTCEPSS rescore
  8. 2026-06-25 10:07 UTCEG score recompute
  9. 2026-06-25 10:07 UTCGHSA enrichment

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 3.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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