CVE-2024-42243: mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray
Noroxi assessment
Priority: Monitor (action score 22/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.21% (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 099d90642a711caae377f53309abfe27e8724a8b, 0c8a837153c15c33f9b4616860331a2dba1120c1, 333c5539a31f48828456aa9997ec2808f06a699a.
Low priority for now. Upgrade to Linux Linux 099d90642a711caae377f53309abfe27e8724a8b, 0c8a837153c15c33f9b4616860331a2dba1120c1, 333c5539a31f48828456aa9997ec2808f06a699a 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/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray Patch series "mm/filemap: Limit page cache size to that supported by xarray", v2. Currently, xarray can't support arbitrary page cache size. More details can be found from the WARN_ON() statement in xas_split_alloc(). In our test whose code is attached below, we hit the WARN_ON() on ARM64 system where the base page size is 64KB and huge page size is 512MB. The issue was reported long time ago and some discussions on it can be found here [1]. [1] https://www.spinics.net/lists/linux-xfs/msg75404.html In order to fix the issue, we need to adjust MAX_PAGECACHE_ORDER to one supported by xarray and avoid PMD-sized page cache if needed. The code changes are suggested by David Hildenbrand. PATCH[1] adjusts MAX_PAGECACHE_ORDER to that supported by xarray PATCH[2-3] avoids PMD-sized page cache in the synchronous readahead path PATCH[4] avoids PMD-sized page cache for shmem files if needed Test program ============ # cat test.c #define _GNU_SOURCE #include <stdio.h> #include <stdlib.h> #include <unistd.h> #include <string.h> #include <fcntl.h> #include <errno.h> #include <sys/syscall.h> #include <sys/mman.h> #define TEST_XFS_FILENAME "/tmp/data" #define TEST_SHMEM_FILENAME "/dev/shm/data" #define TEST_MEM_SIZE 0x20000000 int main(int argc, char **argv) { const char *filename; int fd = 0; void *buf = (void *)-1, *p; int pgsize = getpagesize(); int ret; if (pgsize != 0x10000) { fprintf(stderr, "64KB base page size is required\n"); return -EPERM; } system("echo force > /sys/kernel/mm/transparent_hugepage/shmem_enabled"); system("rm -fr /tmp/data"); system("rm -fr /dev/shm/data"); system("echo 1 > /proc/sys/vm/drop_caches"); /* Open xfs or shmem file */ filename = TEST_XFS_FILENAME; if (argc > 1 && !strcmp(argv[1], "shmem")) filename = TEST_SHMEM_FILENAME; fd = open(filename, O_CREAT | O_RDWR | O_TRUNC); if (fd < 0) { fprintf(stderr, "Unable to open <%s>\n", filename); return -EIO; } /* Extend file size */ ret = ftruncate(fd, TEST_MEM_SIZE); if (ret) { fprintf(stderr, "Error %d to ftruncate()\n", ret); goto cleanup; } /* Create VMA */ buf = mmap(NULL, TEST_MEM_SIZE, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0); if (buf == (void *)-1) { fprintf(stderr, "Unable to mmap <%s>\n", filename); goto cleanup; } fprintf(stdout, "mapped buffer at 0x%p\n", buf); ret = madvise(buf, TEST_MEM_SIZE, MADV_HUGEPAGE); if (ret) { fprintf(stderr, "Unable to madvise(MADV_HUGEPAGE)\n"); goto cleanup; } /* Populate VMA */ ret = madvise(buf, TEST_MEM_SIZE, MADV_POPULATE_WRITE); if (ret) { fprintf(stderr, "Error %d to madvise(MADV_POPULATE_WRITE)\n", ret); goto cleanup; } /* Punch the file to enforce xarray split */ ret = fallocate(fd, FALLOC_FL_KEEP_SIZE | FALLOC_FL_PUNCH_HOLE, TEST_MEM_SIZE - pgsize, pgsize); if (ret) fprintf(stderr, "Error %d to fallocate()\n", ret); cleanup: if (buf != (void *)-1) munmap(buf, TEST_MEM_SIZE); if (fd > 0) close(fd); return 0; } # gcc test.c -o test # cat /proc/1/smaps | grep KernelPageSize | head -n 1 KernelPageSize: 64 kB # ./test shmem : ------------[ cut here ]------------ WARNING: CPU: 17 PID: 5253 at lib/xarray.c:1025 xas_split_alloc+0xf8/0x128 Modules linked in: nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib \ nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct \ nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 \ ip_set nf_tables rfkill nfnetlink vfat fat virtio_balloon \ drm fuse xfs libcrc32c crct10dif_ce ghash_ce sha2_ce sha256_arm64 \ virtio_net sha1_ce net_failover failover virtio_console virtio_blk \ dimlib virtio_mmio CPU: 17 PID: 5253 Comm: test Kdump: loaded Tainted: G W 6.10.0-rc5-gavin+ #12 Hardware name: QEMU KVM Virtual Machine, BIOS edk2-20240524-1.el9 05/24/2024 pstate: 83400005 (Nzcv daif +PAN -UAO +TC ---truncated---
- Published
- Aug 7, 2024
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 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.
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.18 and later · before 6.6.41
- linux linux kernel6.7 and later · before 6.9.10
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
- 5.18affected
- 793917d997df2e432f3e9ac126e4482d68256d01 and later · before 0c8a837153c15c33f9b4616860331a2dba1120c1affected · git
- 793917d997df2e432f3e9ac126e4482d68256d01 and later · before a0c42ddd0969fdc760a85e20e267776028a7ca4eaffected · git
- 793917d997df2e432f3e9ac126e4482d68256d01 and later · before 333c5539a31f48828456aa9997ec2808f06a699aaffected · git
- 793917d997df2e432f3e9ac126e4482d68256d01 and later · before 099d90642a711caae377f53309abfe27e8724a8baffected · git
- before 5.18not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.41 and later · up to and including 6.6.*not affected · semver
- 6.9.10 and later · up to and including 6.9.*not affected · semver
- 6.10 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.9.10-1 | 6.9.10-1 |
| openSUSE:Leap 15.6 | dtb-aarch64 | before 6.4.0-150600.23.25.1 | 6.4.0-150600.23.25.1 |
| openSUSE:Leap 15.6 | kernel-64kb | before 6.4.0-150600.23.25.1 | 6.4.0-150600.23.25.1 |
| openSUSE:Leap 15.6 | kernel-azure | before 6.4.0-150600.8.14.1 | 6.4.0-150600.8.14.1 |
| openSUSE:Leap 15.6 | kernel-debug | before 6.4.0-150600.23.25.1 | 6.4.0-150600.23.25.1 |
| openSUSE:Leap 15.6 | kernel-default | before 6.4.0-150600.23.25.1 | 6.4.0-150600.23.25.1 |
| openSUSE:Leap 15.6 | kernel-default-base | before 6.4.0-150600.23.25.1.150600.12.10.2 | 6.4.0-150600.23.25.1.150600.12.10.2 |
| openSUSE:Leap 15.6 | kernel-docs | before 6.4.0-150600.23.25.2 | 6.4.0-150600.23.25.2 |
| openSUSE:Leap 15.6 | kernel-kvmsmall | before 6.4.0-150600.23.25.1 | 6.4.0-150600.23.25.1 |
| openSUSE:Leap 15.6 | kernel-obs-build | before 6.4.0-150600.23.25.2 | 6.4.0-150600.23.25.2 |
| openSUSE:Leap 15.6 | kernel-obs-qa | before 6.4.0-150600.23.25.1 | 6.4.0-150600.23.25.1 |
| openSUSE:Leap 15.6 | kernel-rt | before 6.4.0-150600.10.14.1 | 6.4.0-150600.10.14.1 |
| openSUSE:Leap 15.6 | kernel-rt_debug | before 6.4.0-150600.10.14.1 | 6.4.0-150600.10.14.1 |
| openSUSE:Leap 15.6 | kernel-source | before 6.4.0-150600.23.25.1 | 6.4.0-150600.23.25.1 |
| openSUSE:Leap 15.6 | kernel-source-azure | before 6.4.0-150600.8.14.1 | 6.4.0-150600.8.14.1 |
| openSUSE:Leap 15.6 | kernel-source-rt | before 6.4.0-150600.10.14.1 | 6.4.0-150600.10.14.1 |
| openSUSE:Leap 15.6 | kernel-syms | before 6.4.0-150600.23.25.1 | 6.4.0-150600.23.25.1 |
| openSUSE:Leap 15.6 | kernel-syms-azure | before 6.4.0-150600.8.14.1 | 6.4.0-150600.8.14.1 |
| openSUSE:Leap 15.6 | kernel-syms-rt | before 6.4.0-150600.10.14.1 | 6.4.0-150600.10.14.1 |
| openSUSE:Leap 15.6 | kernel-zfcpdump | before 6.4.0-150600.23.25.1 | 6.4.0-150600.23.25.1 |
| Red Hat:rhel_eus:9.2::appstream | bpftool-debuginfo | before 0:7.0.0-284.84.1.el9_2 | 0:7.0.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-devel | before 0:5.14.0-284.84.1.el9_2 | 0:5.14.0-284.84.1.el9_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-42239Aug 7, 2024 · bpf: Fail bpf_timer_cancel when callback is being cancelled22Monitor
- ← EarlierCVE-2024-42241Aug 7, 2024 · mm/shmem: disable PMD-sized page cache if needed22Monitor
- Later →CVE-2024-42251Aug 8, 2024 · mm: page_ref: remove folio_try_get_rcu()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 / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 099d90642a711caae377f53309abfe27e8724a8b | Vendor (CNA) |
| Linux Linux | 0c8a837153c15c33f9b4616860331a2dba1120c1 | Vendor (CNA) |
| Linux Linux | 333c5539a31f48828456aa9997ec2808f06a699a | Vendor (CNA) |
| Linux Linux | a0c42ddd0969fdc760a85e20e267776028a7ca4e | Vendor (CNA) |
| debian:linux | 6.9.10-1 · Debian:13 | Package registry (OSV) |
| opensuse:dtb-aarch64 | 6.4.0-150600.23.25.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-64kb | 6.4.0-150600.23.25.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-azure | 6.4.0-150600.8.14.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-debug | 6.4.0-150600.23.25.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-default | 6.4.0-150600.23.25.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-default-base | 6.4.0-150600.23.25.1.150600.12.10.2 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-docs | 6.4.0-150600.23.25.2 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-kvmsmall | 6.4.0-150600.23.25.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-obs-build | 6.4.0-150600.23.25.2 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-obs-qa | 6.4.0-150600.23.25.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-source-azure | 6.4.0-150600.8.14.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-syms-azure | 6.4.0-150600.8.14.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.0.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-284.84.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| suse:kernel-64kb | 6.4.0-150600.23.25.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6 | Package registry (OSV) |
+11
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.
No history yet (it accumulates with the daily EPSS job).
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 researchersFinders, 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.
No nightly-computed relations.
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).
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.