Skip to main content
Mallory
UnratedVulnerability

CVE-2026-101321: Local privilege escalation in FreeBSD compat32 recvmsg control-message handling

Updated 3 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 3 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-101321CWE-362

CVE-2026-101321 is a race condition in FreeBSD's compat32 recvmsg(2) control-message handling. When copying received control messages to a 32-bit process, the implementation temporarily modifies message-header length fields in place. For large control messages received using MSG_PEEK, this storage can remain shared with the socket buffer. Concurrent operations on the same socket can race with the temporary modification, corrupting the socket's message queue and enabling kernel memory corruption and local privilege escalation. Supported FreeBSD versions with COMPAT_FREEBSD32 enabled are affected before the applicable correction.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An unprivileged local user can exploit kernel memory corruption to escalate privileges, potentially compromising system confidentiality, integrity, and availability. The vulnerability has a CVSS v3.0 base score of 7.8, with vector CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Mitigation

If you can’t patch tonight, do this now.

No workaround is available according to the advisory. Kernels compiled without COMPAT_FREEBSD32 are not affected.

Remediation

Patch, then assume compromise.

Upgrade to a corrected FreeBSD kernel and reboot. Corrected versions include 15.2-STABLE, 15.1-RELEASE-p7, 14.5-STABLE, 14.5-RELEASE-p4, and 14.4-RELEASE-p13. Use the supported base-system package or binary update mechanism appropriate to the installation, or verify and apply the official source patch, rebuild the kernel, and reboot.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-101321 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-101321 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-101321?
As of Nov 19, 2026, Mallory has found no public exploit for CVE-2026-101321.
Is there a patch for CVE-2026-101321?
Upgrade to a corrected FreeBSD kernel and reboot. Corrected versions include 15.2-STABLE, 15.1-RELEASE-p7, 14.5-STABLE, 14.5-RELEASE-p4, and 14.4-RELEASE-p13.
Activity feed

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.