A flaw in the Linux kernel’s Open vSwitch datapath shows how a small implementation detail can remain harmless for years before a seemingly unrelated change turns it into a practical privilege-escalation vulnerability.
Security researcher Asim Manizada disclosed OVSwrap (CVE-2026-64531), a memory corruption bug that allows ordinary local users to gain root privileges on many Linux distributions under common default configurations. According to The Hacker News, the exploit does not require an existing Open vSwitch bridge, a running ovs-vswitchd daemon, or host-level CAP_NET_ADMIN.
The vulnerable code resides in the kernel datapath rather than userspace. On systems where the Open vSwitch kernel module is available and unprivileged user namespaces are enabled, a regular user can create isolated user and network namespaces, obtain CAP_NET_ADMIN inside that namespace, and reach the vulnerable code path. Even systems where the module is not currently loaded are not necessarily safe, since resolving the Generic Netlink family name can trigger automatic module loading.
Interestingly, the vulnerable assignment had existed for around 13 years. During that time, another safeguard limited the total generated action stream to 32 KiB, preventing the affected data structure from exceeding the size that would trigger the bug. A change introduced in March 2025 removed that limit to eliminate reliability issues affecting deployments, including large OpenStack environments. While the change improved functionality, it also exposed the older truncation flaw.
The vulnerability stems from a 16-bit length field used for nested Netlink attributes. By constructing a specially crafted action containing hundreds of conntrack sub-actions, an attacker can force the generated data to exceed 65,535 bytes. The recorded length then wraps around, causing later parsing code to interpret attacker-controlled data as legitimate Open vSwitch actions. Because the parser lands at a predictable location inside the same buffer, the exploit does not require complex heap grooming techniques often associated with kernel memory corruption.
The released proof-of-concept chains several primitives together, including leaking kernel pointers, performing arbitrary kernel reads, and modifying kernel credentials until they grant root access. The exploit is intentionally destructive: on success it alters the system’s sudo configuration, launches a root shell, and deliberately leaves modified kernel state behind instead of attempting a clean teardown.
Another notable aspect is the breadth of tested systems. The researcher reported successful exploitation on numerous mainstream distributions, including Debian 12 and 13, Ubuntu 22.04, Fedora 42–44, Arch, Alpine 3.22–3.24, Amazon Linux 2023, CentOS Stream 9 and 10, Rocky Linux 9 and 10, Linux Mint 22.3, Kali 2026.1, NixOS, Gentoo, Pop!_OS, openSUSE Tumbleweed, and AlmaLinux 9 and 10. Ubuntu 24.04 required bypassing AppArmor restrictions using the proof-of-concept’s fallback mechanism, while stock Ubuntu 26.04 blocked the ordinary-user attack path unless its AppArmor user-namespace restriction was disabled. Older releases such as Debian 11, Rocky Linux 8, Ubuntu 20.04, and Amazon Linux 2 were reported as not exploitable through this technique.
Upstream fixes became available in stable kernel releases on July 24, but distribution maintainers may backport patches independently, making vendor advisories the most reliable way to determine whether a system is protected. For systems that do not require Open vSwitch, preventing the kernel module from loading provides an effective interim mitigation, although already-loaded modules must still be unloaded or removed by rebooting. Disabling unprivileged user namespaces also blocks the ordinary local-user attack path, though it does not prevent attacks from processes that already possess CAP_NET_ADMIN inside attacker-controlled network namespaces.
The vulnerability serves as a reminder that security issues are not always introduced by new code. Sometimes an old bug remains dormant for years until another change removes the assumptions that quietly kept it out of reach.