CVE-2026-53227
net: 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.
INFO
Published Date :
June 25, 2026, 9:16 a.m.
Last Modified :
July 2, 2026, 8:37 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Set pointer to NULL after saving its error value.
- Apply the vendor-provided patch to the Linux kernel.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-53227.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-53227 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-53227
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-53227 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-53227 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Jul. 02, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Added CWE CWE-401 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.176 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.143 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.210 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.36 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.94 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 7.0.13 *cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc6:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc7:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 3.16 up to (excluding) 5.10.259 Added Reference Type kernel.org: https://git.kernel.org/stable/c/0bb5b2dc1b90aa7dd1473fc8c4d813a29255ff8d Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/25fdf53698535fe8790237f5a8a9626791429785 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/895d1dd9057cde1687fa0f4286d47ceed0b82997 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/971b1b37774f13acc5add0a2843f8598446b8598 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/e248fb2e680deb2bd37bac551b72638fe4938a76 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/e3d509a1b71396e1452060dbf84a805fd1c3c549 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/ecc55aad3390129a87106841f4b68bf3d70c9264 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/ee30dd2909d8b98619f4341c70ec8dc8e155ab02 Types: Patch -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 25, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '893f139b9a6c00c097b9082a90f3041cfb3a0d20', 'lessThan': 'e248fb2e680deb2bd37bac551b72638fe4938a76', 'versionType': 'git'}, {'status': 'affected', 'version': '893f139b9a6c00c097b9082a90f3041cfb3a0d20', 'lessThan': '0bb5b2dc1b90aa7dd1473fc8c4d813a29255ff8d', 'versionType': 'git'}, {'status': 'affected', 'version': '893f139b9a6c00c097b9082a90f3041cfb3a0d20', 'lessThan': '971b1b37774f13acc5add0a2843f8598446b8598', 'versionType': 'git'}, {'status': 'affected', 'version': '893f139b9a6c00c097b9082a90f3041cfb3a0d20', 'lessThan': '25fdf53698535fe8790237f5a8a9626791429785', 'versionType': 'git'}, {'status': 'affected', 'version': '893f139b9a6c00c097b9082a90f3041cfb3a0d20', 'lessThan': 'e3d509a1b71396e1452060dbf84a805fd1c3c549', 'versionType': 'git'}, {'status': 'affected', 'version': '893f139b9a6c00c097b9082a90f3041cfb3a0d20', 'lessThan': 'ecc55aad3390129a87106841f4b68bf3d70c9264', 'versionType': 'git'}, {'status': 'affected', 'version': '893f139b9a6c00c097b9082a90f3041cfb3a0d20', 'lessThan': '895d1dd9057cde1687fa0f4286d47ceed0b82997', 'versionType': 'git'}, {'status': 'affected', 'version': '893f139b9a6c00c097b9082a90f3041cfb3a0d20', 'lessThan': 'ee30dd2909d8b98619f4341c70ec8dc8e155ab02', 'versionType': 'git'}], 'programFiles': ['net/openvswitch/datapath.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '3.16'}, {'status': 'unaffected', 'version': '0', 'lessThan': '3.16', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.259', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.210', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.176', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.143', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.94', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.36', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.13', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['net/openvswitch/datapath.c'], 'defaultStatus': 'affected'}] Added 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. Added Reference https://git.kernel.org/stable/c/0bb5b2dc1b90aa7dd1473fc8c4d813a29255ff8d Added Reference https://git.kernel.org/stable/c/25fdf53698535fe8790237f5a8a9626791429785 Added Reference https://git.kernel.org/stable/c/895d1dd9057cde1687fa0f4286d47ceed0b82997 Added Reference https://git.kernel.org/stable/c/971b1b37774f13acc5add0a2843f8598446b8598 Added Reference https://git.kernel.org/stable/c/e248fb2e680deb2bd37bac551b72638fe4938a76 Added Reference https://git.kernel.org/stable/c/e3d509a1b71396e1452060dbf84a805fd1c3c549 Added Reference https://git.kernel.org/stable/c/ecc55aad3390129a87106841f4b68bf3d70c9264 Added Reference https://git.kernel.org/stable/c/ee30dd2909d8b98619f4341c70ec8dc8e155ab02