CVE-2026-53227 Details
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.
A vulnerability in the Linux kernel's Open vSwitch component can lead to improper memory management. Specifically, when the 'reply' socket buffer (skb) is allocated after locking the Open vSwitch mutex and the allocation fails, it leaves an invalid pointer error. The subsequent cleanup process attempts to free this invalid pointer, potentially causing a memory error. This issue arises because error cleanups assume the 'reply' is allocated before the mutex is locked, leading to a reversal in the expected order of operations.
The vulnerability has been addressed by modifying the error handling process. The 'reply' pointer is now set to NULL after an allocation error is detected, preventing the cleanup stage from attempting to free an invalid pointer.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/0bb5b2dc1b90aa7dd1473fc8c4d813a29255ff8d | kernel.org | Patch |
| https://git.kernel.org/stable/c/25fdf53698535fe8790237f5a8a9626791429785 | kernel.org | Patch |
| https://git.kernel.org/stable/c/895d1dd9057cde1687fa0f4286d47ceed0b82997 | kernel.org | Patch |
| https://git.kernel.org/stable/c/971b1b37774f13acc5add0a2843f8598446b8598 | kernel.org | Patch |
| https://git.kernel.org/stable/c/e248fb2e680deb2bd37bac551b72638fe4938a76 | kernel.org | Patch |
| https://git.kernel.org/stable/c/e3d509a1b71396e1452060dbf84a805fd1c3c549 | kernel.org | Patch |
| https://git.kernel.org/stable/c/ecc55aad3390129a87106841f4b68bf3d70c9264 | kernel.org | Patch |
| https://git.kernel.org/stable/c/ee30dd2909d8b98619f4341c70ec8dc8e155ab02 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-401 | Missing Release of Memory after Effective Lifetime | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 3.16, < 5.10.259 >= 5.11, < 5.15.210 >= 5.16, < 6.1.176 >= 6.2, < 6.6.143 >= 6.7, < 6.12.94 >= 6.13, < 6.18.36 >= 6.19, < 7.0.13 7.1 rc1 7.1 rc2 7.1 rc3 7.1 rc4 7.1 rc5 7.1 rc6 7.1 rc7 |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 2, 2026 | Initial Analysis | [email protected] |
| Jun 25, 2026 | New CVE Received | kernel.org |