Loading vulnerability…
A vulnerability in the Linux kernel's Visconti clock driver (clk: visconti) allowed for an array overflow in the visconti_clk_register_gates() function. The issue arose because the code used -1 to indicate the absence of a reset function, but stored this value in a u8 type, causing the check if (clks[i].rs_id >= 0) to always evaluate as true. This led to out-of-bounds access when registering clock gates.
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 provides a full proof-of-concept (POC) local privilege escalation exploit for CVE-2022-49186, a vulnerability in the Linux kernel's visconti_clk driver (5.17.0-5.17.1). The exploit is implemented in C (exploit/exploit.c) and targets a signed-to-unsigned conversion bug in the kernel module (vulnerable-module/visconti_clk.c), which allows an attacker to overflow an array and corrupt adjacent memory, ultimately enabling arbitrary code execution in kernel context. The exploit works by writing a specially crafted structure to the device file /dev/visconti_clk, then using IOCTLs to trigger the privilege escalation. Upon success, the exploit spawns a root shell. The repository also includes setup scripts and documentation for building and testing the exploit in a controlled environment. The attack vector is local, requiring the attacker to have access to a shell on the target system. No network endpoints are involved. The exploit is a POC and not weaponized, but demonstrates the full exploitation chain from vulnerability to root shell.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.