Out-of-bounds write in Zephyr recvmsg() ancillary data handling
CVE-2026-10643 is a memory corruption vulnerability in Zephyr’s IP socket recvmsg() ancillary-data handling, specifically in insert_pktinfo() in subsys/net/lib/sockets/sockets_inet.c. The implementation validated the user-supplied msg_control buffer using only the ancillary payload length (msg->msg_controllen < pktinfo_len) before writing a full control message composed of an aligned cmsg header plus payload. Because the check omitted the cmsg header size, undersized control buffers could pass validation and then be overrun during control message construction. For example, for IPv4 IP_PKTINFO on a 64-bit target, buffers in the 16-27 byte range can pass the check even though one control message element requires 28 bytes. This results in a fixed-size out-of-bounds write of up to approximately one cmsg header (~12 bytes) past the end of the buffer. In CONFIG_USERSPACE builds, recvmsg verification allocates a kernel-heap copy of the control buffer sized to msg_controllen and executes the vulnerable path against it, making the overflow a kernel-heap corruption reachable by an unprivileged userspace thread. In supervisor mode, the overflow corrupts the caller-provided buffer. Affected versions are Zephyr v3.6.0 through v4.4.0.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.