Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2024-42243— mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray

Quick assessment

Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel 存在安全漏洞,该漏洞源于 mm/filemap 模块的xarray无法接受任意的页面缓存大小。在ARM64系统上,基础页面大小为64KB,大页面大小为512MB时,会触发WARN_ON警告。

AI Predicted 4.4 Difficulty: Moderate EPSS 0.21% · P12

Possible ATT&CK Techniques 1 AI

T1498 · Network Denial of Service

Affected Version Matrix 8

VendorProduct Version RangeStatus
Linux Linux 793917d997df2e432f3e9ac126e4482d68256d01< a0c42ddd0969fdc760a85e20e267776028a7ca4e affected
793917d997df2e432f3e9ac126e4482d68256d01< 333c5539a31f48828456aa9997ec2808f06a699a affected
793917d997df2e432f3e9ac126e4482d68256d01< 099d90642a711caae377f53309abfe27e8724a8b affected
5.18 affected
< 5.18 unaffected
6.6.41≤ 6.6.* unaffected
6.9.10≤ 6.9.* unaffected
6.10≤ * unaffected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2024-42243

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
mm/filemap: make MAX_PAGECACHE_ORDER acceptable to xarray
Source: CVE Program / CVE List V5
Vulnerability Description
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---
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel 存在安全漏洞,该漏洞源于 mm/filemap 模块的xarray无法接受任意的页面缓存大小。在ARM64系统上,基础页面大小为64KB,大页面大小为512MB时,会触发WARN_ON警告。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
Linux Linux 793917d997df2e432f3e9ac126e4482d68256d01 ~ a0c42ddd0969fdc760a85e20e267776028a7ca4e -
Linux Linux 5.18 -

II. Public POCs for CVE-2024-42243

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-42243

登录查看更多情报信息。

Same Patch Batch · Linux · 2024-08-07 · 19 CVEs total

CVE-2024-42232 9.8 CRITICAL libceph: fix race between delayed_work() and ceph_monc_stop()
CVE-2024-42249 7.8 HIGH spi: don't unoptimize message in spi_async()
CVE-2024-42234 7.8 HIGH mm: fix crashes from deferred split racing folio migration
CVE-2024-42233 7.8 HIGH filemap: replace pte_offset_map() with pte_offset_map_nolock()
CVE-2024-42235 7.8 HIGH s390/mm: Add NULL pointer check to crst_table_free() base_crst_free()
CVE-2024-42236 7.8 HIGH usb: gadget: configfs: Prevent OOB read/write in usb_string_copy()
CVE-2024-42250 7.8 HIGH cachefiles: add missing lock protection when polling
CVE-2024-42247 7.5 HIGH wireguard: allowedips: avoid unaligned 64-bit memory accesses
CVE-2024-42240 x86/bhi: Avoid warning in #DB handler due to BHI mitigation
CVE-2024-42237 firmware: cs_dsp: Validate payload length before processing block
CVE-2024-42238 firmware: cs_dsp: Return error if block header overflows file
CVE-2024-42239 bpf: Fail bpf_timer_cancel when callback is being cancelled
CVE-2024-42242 mmc: sdhci: Fix max_seg_size for 64KiB PAGE_SIZE
CVE-2024-42241 mm/shmem: disable PMD-sized page cache if needed
CVE-2024-42244 USB: serial: mos7840: fix crash on resume
CVE-2024-42245 Revert "sched/fair: Make sure to try to detach at least one movable task"
CVE-2024-42246 net, sunrpc: Remap EPERM in case of connection failure in xs_tcp_setup_socket
CVE-2024-42248 tty: serial: ma35d1: Add a NULL check for of_node

IV. Related Vulnerabilities

V. Comments for CVE-2024-42243

No comments yet


Leave a comment