Skip to main content
Mallory
MediumVulnerability

CVE-2026-49424: Linuxulator waitid() Uninitialized Kernel Stack Disclosure

Published Aug 19, 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.
CVSS5.5Medium · v3.1
EPSS0.15%4th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
FreebsdLinux
IdentifiersCVE-2026-49424CWE-457

CVE-2026-49424 is an information-disclosure vulnerability in FreeBSD's Linux binary compatibility layer (Linuxulator). The Linux waitid() implementation translates a native FreeBSD siginfo_t structure into a stack-allocated Linux siginfo_t structure without first initializing the destination structure. Fields not populated during translation can retain kernel-stack contents and be exposed to an unprivileged caller.

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 observe 104 bytes of uninitialized kernel-stack memory. Disclosed data may include sensitive kernel-resident information and could assist further exploitation by weakening kernel address-space or state confidentiality.

Mitigation

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

No workaround is available for systems that require the Linux binary compatibility layer. Systems where Linuxulator is not loaded or used are not vulnerable; administrators can remove or avoid loading Linux binary compatibility support where operationally feasible.

Remediation

Patch, then assume compromise.

Update FreeBSD to a supported stable or release/security branch containing the vendor correction for CVE-2026-49424, then reboot into the updated kernel. Available vendor-supported update methods include binary base-system updates, base-system package updates where applicable, or applying the vendor patch followed by a kernel rebuild 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.
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
LinuxLinux Kerneloperating_system
FAQ

Frequently asked questions

Is CVE-2026-49424 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-49424 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-49424?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-49424.
Is there a patch for CVE-2026-49424?
Update FreeBSD to a supported stable or release/security branch containing the vendor correction for CVE-2026-49424, then reboot into the updated kernel. Available vendor-supported update methods include binary base-system updates, base-system package updates where applicable, or applying the vendor patch followed by a kernel rebuild and reboot.
What products are affected by CVE-2026-49424?
Freebsd and Linux Kernel.
How severe is CVE-2026-49424?
CVE-2026-49424 has a CVSS v3.1 score of 5.5 (Medium) and an EPSS score of 0.15% (4th 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 activity4Community discussion across Reddit, Mastodon, and other social sources.