Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ee30dd2909d8b98619f4341c70ec8dc8e155ab02 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:49 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in ee30dd2909d8b98619f4341c70ec8dc8e155ab02, ecc55aad3390129a87106841f4b68bf3d70c9264, e248fb2e680deb2bd37bac551b72638fe4938a76 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 893f139b9a6c00c097b9082a90f3041cfb3a0d20, < ee30dd2909d8b98619f4341c70ec8dc8e155ab02
Fixed in
  • ee30dd2909d8b98619f4341c70ec8dc8e155ab02
LinuxLinuxAffected
  • ≥ 893f139b9a6c00c097b9082a90f3041cfb3a0d20, < ecc55aad3390129a87106841f4b68bf3d70c9264
Fixed in
  • ecc55aad3390129a87106841f4b68bf3d70c9264
LinuxLinuxAffected
  • ≥ 893f139b9a6c00c097b9082a90f3041cfb3a0d20, < e248fb2e680deb2bd37bac551b72638fe4938a76
Fixed in
  • e248fb2e680deb2bd37bac551b72638fe4938a76
LinuxLinuxAffected
  • ≥ 893f139b9a6c00c097b9082a90f3041cfb3a0d20, < e3d509a1b71396e1452060dbf84a805fd1c3c549
Fixed in
  • e3d509a1b71396e1452060dbf84a805fd1c3c549
LinuxLinuxAffected
  • ≥ 893f139b9a6c00c097b9082a90f3041cfb3a0d20, < 971b1b37774f13acc5add0a2843f8598446b8598
Fixed in
  • 971b1b37774f13acc5add0a2843f8598446b8598
LinuxLinuxAffected
  • ≥ 893f139b9a6c00c097b9082a90f3041cfb3a0d20, < 895d1dd9057cde1687fa0f4286d47ceed0b82997
Fixed in
  • 895d1dd9057cde1687fa0f4286d47ceed0b82997

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.

References

Community reviews

Loading reviews…