CVE-2026-53227
Last modified
CVE-2026-53227 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.20% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 3.16, < 5.10.259 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.210 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.176 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.143 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.94 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.36 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.13 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53227?
How severe is CVE-2026-53227?
How do I fix CVE-2026-53227?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53221In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53222In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53223In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-53224In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-53225In the Linux kernel, the following vulnerability has been re…9.1
- CVE-2026-53226In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53228In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-53229In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-5323A vulnerability was found in priyankark a11y-mcp up to 1.0.5…5.3
- CVE-2026-53230In the Linux kernel, the following vulnerability has been re…8.7
- CVE-2026-53231In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53232In the Linux kernel, the following vulnerability has been re…8.8
Are you affected by CVE-2026-53227?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST