Loading vulnerability…
In uutils coreutils, the recursive mode (-R) of the chmod utility incorrectly computes its process exit status when operating on multiple files. Errors encountered on earlier files during traversal are not preserved; instead, the final return value is determined only by whether the last processed file succeeded or failed. As a result, chmod -R can return exit code 0 even when prior operations failed with errors such as 'Operation not permitted'. This is a logic flaw in error handling/reporting rather than a direct memory-safety issue, and it can mislead callers into believing a recursive permission change completed successfully when it did not.
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.
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.