A vulnerability in FreeBSD's msdosfs(5) implementation, present in certain 12.x and 11.x releases, fails to zero-fill two padding fields in the dirent structure. This results in a leak of three uninitialized bytes from kernel memory to user space when directory entries are read from an msdosfs filesystem.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains two C proof-of-concept (PoC) exploits and a detailed README describing information disclosure vulnerabilities in the FreeBSD kernel's handling of directory entries (struct dirent) in several filesystems (msdosfs, mqueuefs, tmpfs, smbfs, autofs). The vulnerabilities allow uninitialized kernel memory, including potential kernel pointers, to be leaked to userspace via the readdir() system call. The repository structure is as follows: - README.md: Provides a thorough explanation of the vulnerability, affected filesystems, and instructions for setting up a test environment and running the PoCs. - original_poc.c: A PoC targeting msdosfs, which repeatedly opens and reads a directory, checking for non-zero values in the padding fields of struct dirent and printing leaked bytes if found. - variants_poc.c: A PoC for variant filesystems (e.g., mqueuefs), which checks for non-zero values in the d_off field of struct dirent and prints leaked kernel memory. The exploits require local access to a FreeBSD system with the relevant filesystem mounted. They demonstrate the ability to leak uninitialized kernel memory to userspace, which could be used for further exploitation (e.g., bypassing KASLR or leaking sensitive data). No network endpoints or remote attack vectors are present; the attack is purely local and filesystem-based.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.