Loading vulnerability…
CVE-2026-80724 is an access-control flaw in the Linux kernel vmclock miscellaneous-device mmap implementation. Although the implementation rejects an initially writable mapping of the shared vmclock ABI page, it leaves the VM_MAYWRITE capability set when a process maps the page read-only. A guest process can consequently use mprotect() to upgrade that mapping to writable and alter vmclock data that is intended to be host-written and read-only, including the sequence counter, UTC time, and TSC offset.
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 is a small standalone C proof-of-concept and technical write-up for CVE-2026-80724; it is not part of an exploitation framework. The repository contains seven files: root and CVE-specific README files, a detailed Markdown write-up, a Makefile, the C PoC, a .gitignore, and an MIT license. The build process compiles CVE-2026-80724/vmclock_poc.c into vmclock_poc. The PoC targets a local Linux guest using the ptp_vmclock driver. It opens /dev/vmclock0 (or a caller-provided vmclock device), maps one 4096-byte vmclock ABI page with PROT_READ and MAP_SHARED, then invokes mprotect() to request PROT_READ|PROT_WRITE. On vulnerable kernels, the driver rejected writable mappings initially but left VM_MAYWRITE set, allowing this later protection upgrade. A first write fault on the PFNMAP mapping can then make the PTE writable, permitting writes to memory that is supposed to be host-owned and guest-read-only. After dumping vmclock metadata, the PoC writes the sequence counter and disruption marker, reads the marker back to confirm success, and restores both original values. It handles SIGSEGV to classify a write fault as patched or mitigated. The exploit is operational rather than merely a detector because it deliberately performs and verifies memory corruption, although its hardcoded payload is limited to vmclock timekeeping fields and does not provide code execution, privilege escalation, persistence, or network functionality.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel PTP vmclock flaw in which the shared vmclock ABI page could be mapped read-only and subsequently made writable using mprotect() because VM_MAYWRITE remained set. A guest could then corrupt host-written timekeeping data, including the sequence counter, UTC time, and TSC offset.
A critical-severity, remotely exploitable vulnerability tracked as CVE-2026-80724. The supplied CVSS v3.0 vector indicates network attack vector, low attack complexity, no privileges or user interaction required, and high confidentiality, integrity, and availability impact. The content associates it with Debian Linux 14.0.
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.