CVE-2026-53227: net: openvswitch: fix possible kfree_skb of ERR_PTR
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 ovsmutex.
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 ERRPTR, 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.143.1-1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-53227?
The severity of CVE-2026-53227 is medium with a score of 5.5.
How do I fix CVE-2026-53227?
To fix CVE-2026-53227, ensure that you apply the latest patches provided in the Linux kernel updates.
What systems are affected by CVE-2026-53227?
CVE-2026-53227 affects the Linux kernel, specifically in the Open vSwitch component.
What type of vulnerability is CVE-2026-53227?
CVE-2026-53227 is a vulnerability related to possible improper handling of memory management in the networking stack.
Is CVE-2026-53227 easily exploitable?
CVE-2026-53227 has a low attack complexity and requires local access, making it less likely to be exploited remotely.