Loading vulnerability…
A vulnerability in the Linux kernel's User-Mode Linux (um) implementation was identified and resolved, where the syscall_stub_data() function incorrectly interpreted the data_count parameter as a number of bytes instead of longs. This led to an out-of-bounds read on the stack during LDT (Local Descriptor Table) setup, specifically in the init_new_ldt function. The bug was detected by KASAN, which reported a stack-out-of-bounds read of size 128. The vulnerable code path involves memory copying operations that could read beyond the intended stack buffer, potentially exposing sensitive stack data or causing a kernel panic.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel User-Mode Linux out-of-bounds read vulnerability during LDT setup.
An out-of-bounds read vulnerability in Linux kernel User-Mode Linux (UM) LDT setup.
An out-of-bounds read vulnerability in Linux kernel User-Mode Linux (UML) LDT setup handling.
An out-of-bounds read flaw in User-Mode Linux (UM) LDT setup in the Linux kernel.
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.