In FreeBSD 12.0-STABLE before r349628, 12.0-RELEASE before 12.0-RELEASE-p7, 11.3-PRERELEASE before r349629, 11.3-RC3 before 11.3-RC3-p1, and 11.2-RELEASE before 11.2-RELEASE-p11, a bug in the cdrom (cd(4)) driver allows a local user with read access to the cdrom device to trigger an arbitrary overwrite of kernel memory via the driver interface when media is present. This kernel-memory corruption can be leveraged by a malicious user (notably in the operator group, which commonly has device read access) to escalate privileges to root.
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 a single C source file, 'exploit.c', which implements a local privilege escalation exploit targeting UNIX-like systems (likely FreeBSD) with a vulnerable CD-ROM device driver. The exploit works by creating a large number of child processes, each manipulating user credentials, and then performing a series of IOCTL calls to the '/dev/cd0' device. The IOCTL is crafted to reference a specific kernel memory address, and the exploit attempts to escalate privileges by corrupting kernel memory structures. The exploit requires the user to be in the 'operator' group to access the device and assumes the presence of the '/dev/cd0' device. If successful, the exploit will grant root privileges to one of the child processes. The repository is a proof-of-concept and does not include weaponized or framework-based code. The only fingerprintable endpoints are the '/dev/cd0' device file and the '/memory' shared memory object used for process coordination.
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.