Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-53227net: openvswitch: fix possible kfree_skb of ERR_PTR

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53227, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 893f139b9a6c00c097b9082a90f3041cfb3a0d20 – < e248fb2e680deb2bd37bac551b72638fe4938a76
    • affected 893f139b9a6c00c097b9082a90f3041cfb3a0d20 – < 0bb5b2dc1b90aa7dd1473fc8c4d813a29255ff8d
    • affected 893f139b9a6c00c097b9082a90f3041cfb3a0d20 – < 971b1b37774f13acc5add0a2843f8598446b8598
    • affected 893f139b9a6c00c097b9082a90f3041cfb3a0d20 – < 25fdf53698535fe8790237f5a8a9626791429785
    • affected 893f139b9a6c00c097b9082a90f3041cfb3a0d20 – < e3d509a1b71396e1452060dbf84a805fd1c3c549
    • affected 893f139b9a6c00c097b9082a90f3041cfb3a0d20 – < ecc55aad3390129a87106841f4b68bf3d70c9264
    • affected 893f139b9a6c00c097b9082a90f3041cfb3a0d20 – < 895d1dd9057cde1687fa0f4286d47ceed0b82997
    • affected 893f139b9a6c00c097b9082a90f3041cfb3a0d20 – < ee30dd2909d8b98619f4341c70ec8dc8e155ab02
  • Linux · Linux

    • affected 3.16
    • unaffected < 3.16
    • unaffected 5.10.259 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.94 – ≤ 6.12.*
    • unaffected 6.18.36 – ≤ 6.18.*
    • unaffected 7.0.13 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53227 badge
[![CVE-2026-53227](https://cveledger.app/badge/CVE-2026-53227.svg)](https://cveledger.app/cve/CVE-2026-53227)

Record last updated .