CVE-2023-6546 is a race condition in the Linux kernel GSM 0710 tty multiplexer. Concurrent execution of the GSMIOC_SETCONF ioctl by two threads using the same tty file descriptor while the GSM line discipline is enabled can race during GSM multiplexer restart. The race can free a struct gsm_dlci while it remains in use, creating a use-after-free condition.
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 local privilege escalation exploit for CVE-2023-6546, targeting a race condition in the n_gsm TTY line discipline in the Linux kernel. The exploit is implemented in a single C file ('exploit.c') and is designed to work on Ubuntu 18.04/20.04, CentOS 8, and RHEL 8 systems with the n_gsm kernel module loaded. The exploit works by orchestrating a complex race condition to achieve a use-after-free (UAF) on a kernel structure, which is then exploited to execute arbitrary code in kernel context. The payload sets the setuid bit on /usr/bin/python3, allowing the attacker to spawn a root shell. The exploit is operational and includes hardcoded payload logic, but is not part of a framework. The only other file is a minimal README. The exploit must be run locally on the target system and does not require network access.
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.
20 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.