Skip to main content
Mallory
HighVulnerability

CVE-2026-49412: Use-after-free in FreeBSD IPV6_MSFILTER handler

Published Jun 27, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS0.15%5th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Freebsd
IdentifiersCVE-2026-49412CWE-416 · Use After Free

CVE-2026-49412 is a kernel use-after-free vulnerability in FreeBSD's IPv6 multicast subsystem, specifically in the IPV6_MSFILTER socket option handler. The handler drops a serializing lock while copying the source-filter list from userspace and then reacquires it. During that unlocked window, a concurrent thread can free the multicast filter structure, leaving the handler with a stale pointer to freed memory when execution resumes. This creates a race condition that can be triggered by a local unprivileged user and may result in reuse of freed kernel memory in a privileged context.

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.

Successful exploitation can allow an unprivileged local user to escalate privileges on the affected FreeBSD system. Because the flaw is a kernel-space use-after-free involving stale access to freed memory, exploitation may also risk kernel memory corruption and system instability, although the provided advisory specifically states privilege escalation as the security impact.

Mitigation

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

No workaround is available.

Remediation

Patch, then assume compromise.

Apply the FreeBSD security updates that correct the IPV6_MSFILTER handler race and reboot the system. The advisory states fixes are available in 15.1-STABLE after 2026-06-09 19:17:32 UTC, 15.1-RC3-p1, 15.0-RELEASE-p10, 14.4-STABLE after 2026-06-09 19:17:49 UTC, 14.4-RELEASE-p6, and 14.3-RELEASE-p15. FreeBSD indicates systems can be updated via pkg upgrade -r FreeBSD-base, freebsd-update fetch/install, or by applying the provided source patches for 15.1, 15.0, or 14.x, recompiling the kernel, and rebooting.

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.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FreebsdFreebsdoperating_system
FAQ

Frequently asked questions

Is CVE-2026-49412 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-49412 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-49412?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-49412.
Is there a patch for CVE-2026-49412?
Apply the FreeBSD security updates that correct the IPV6_MSFILTER handler race and reboot the system. The advisory states fixes are available in 15.1-STABLE after 2026-06-09 19:17:32 UTC, 15.1-RC3-p1, 15.0-RELEASE-p10, 14.4-STABLE after 2026-06-09 19:17:49 UTC, 14.4-RELEASE-p6, and 14.3-RELEASE-p15.
What products are affected by CVE-2026-49412?
Freebsd.
How severe is CVE-2026-49412?
CVE-2026-49412 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.15% (5th percentile) as of Sep 25, 2026.
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 activity3Community discussion across Reddit, Mastodon, and other social sources.