Loading vulnerability…
CVE-2024-47745 is a Linux kernel protection-mechanism failure in the remap_file_pages() system-call handler. The handler invoked do_mmap() directly without first calling the security_mmap_file() Linux Security Module hook. A process that enables the READ_IMPLIES_EXEC personality and uses remap_file_pages() on a writable file-backed mapping can consequently obtain a writable and executable mapping, bypassing an SELinux-enforced W^X policy. The fix invokes security_mmap_file() with the requested protection before do_mmap() is called.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel memory-management flaw in which remap_file_pages() did not call the security_mmap_file() LSM hook.
A Linux kernel remap_file_pages() flaw that could bypass SELinux-enforced W^X memory-execution policy by remapping writable pages as RWX when READ_IMPLIES_EXEC is set. The fix invokes the security_mmap_file() LSM hook before do_mmap().
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.