Executive Summary

Informations
Name CVE-2024-42241 First vendor Publication 2024-08-07
Vendor Cve Last vendor Modification 2024-08-08

Security-Database Scoring CVSS v3

Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Overall CVSS Score 5.5
Base Score 5.5 Environmental Score 5.5
impact SubScore 3.6 Temporal Score 5.5
Exploitabality Sub Score 1.8
 
Attack Vector Local Attack Complexity Low
Privileges Required Low User Interaction None
Scope Unchanged Confidentiality Impact None
Integrity Impact None Availability Impact High
Calculate full CVSS 3.0 Vectors scores

Security-Database Scoring CVSS v2

Cvss vector :
Cvss Base Score N/A Attack Range N/A
Cvss Impact Score N/A Attack Complexity N/A
Cvss Expoit Score N/A Authentication N/A
Calculate full CVSS 2.0 Vectors scores

Detail

In the Linux kernel, the following vulnerability has been resolved:

mm/shmem: disable PMD-sized page cache if needed

For shmem files, it's possible that PMD-sized page cache can't be supported by xarray. For example, 512MB page cache on ARM64 when the base page size is 64KB can't be supported by xarray. It leads to errors as the following messages indicate when this sort of xarray entry is split.

WARNING: CPU: 34 PID: 7578 at lib/xarray.c:1025 xas_split_alloc+0xf8/0x128 Modules linked in: binfmt_misc 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 rfkill nf_tables nfnetlink vfat fat virtio_balloon drm fuse xfs \ libcrc32c crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce virtio_net \ net_failover virtio_console virtio_blk failover dimlib virtio_mmio CPU: 34 PID: 7578 Comm: test Kdump: loaded Tainted: G W 6.10.0-rc5-gavin+ #9 Hardware name: QEMU KVM Virtual Machine, BIOS edk2-20240524-1.el9 05/24/2024 pstate: 83400005 (Nzcv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--) pc : xas_split_alloc+0xf8/0x128 lr : split_huge_page_to_list_to_order+0x1c4/0x720 sp : ffff8000882af5f0 x29: ffff8000882af5f0 x28: ffff8000882af650 x27: ffff8000882af768 x26: 0000000000000cc0 x25: 000000000000000d x24: ffff00010625b858 x23: ffff8000882af650 x22: ffffffdfc0900000 x21: 0000000000000000 x20: 0000000000000000 x19: ffffffdfc0900000 x18: 0000000000000000 x17: 0000000000000000 x16: 0000018000000000 x15: 52f8004000000000 x14: 0000e00000000000 x13: 0000000000002000 x12: 0000000000000020 x11: 52f8000000000000 x10: 52f8e1c0ffff6000 x9 : ffffbeb9619a681c x8 : 0000000000000003 x7 : 0000000000000000 x6 : ffff00010b02ddb0 x5 : ffffbeb96395e378 x4 : 0000000000000000 x3 : 0000000000000cc0 x2 : 000000000000000d x1 : 000000000000000c x0 : 0000000000000000 Call trace:
xas_split_alloc+0xf8/0x128
split_huge_page_to_list_to_order+0x1c4/0x720
truncate_inode_partial_folio+0xdc/0x160
shmem_undo_range+0x2bc/0x6a8
shmem_fallocate+0x134/0x430
vfs_fallocate+0x124/0x2e8
ksys_fallocate+0x4c/0xa0
__arm64_sys_fallocate+0x24/0x38
invoke_syscall.constprop.0+0x7c/0xd8
do_el0_svc+0xb4/0xd0
el0_svc+0x44/0x1d8
el0t_64_sync_handler+0x134/0x150
el0t_64_sync+0x17c/0x180

Fix it by disabling PMD-sized page cache when HPAGE_PMD_ORDER is larger than MAX_PAGECACHE_ORDER. As Matthew Wilcox pointed, the page cache in a shmem file isn't represented by a multi-index entry and doesn't have this limitation when the xarry entry is split until commit 6b24ca4a1a8d ("mm: Use multi-index entries in the page cache").

Original Source

Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-42241

CWE : Common Weakness Enumeration

% Id Name
100 % CWE-770 Allocation of Resources Without Limits or Throttling

CPE : Common Platform Enumeration

TypeDescriptionCount
Application 8
Os 3658

Sources (Detail)

https://git.kernel.org/stable/c/93893eacb372b0a4a30f7de6609b08c3ba6c4fd9
https://git.kernel.org/stable/c/9fd154ba926b34c833b7bfc4c14ee2e931b3d743
https://git.kernel.org/stable/c/cd25208ca9b0097f8e079d692fc678f36fdbc3f9
Source Url

Alert History

If you want to see full details history, please login or register.
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Date Informations
2025-03-29 03:39:03
  • Multiple Updates
2025-03-28 13:43:53
  • Multiple Updates
2025-03-28 03:17:27
  • Multiple Updates
2025-03-19 03:12:50
  • Multiple Updates
2025-03-18 03:25:45
  • Multiple Updates
2025-03-14 03:13:04
  • Multiple Updates
2025-03-06 14:09:35
  • Multiple Updates
2025-02-22 03:23:06
  • Multiple Updates
2025-01-08 03:04:13
  • Multiple Updates
2025-01-07 03:03:46
  • Multiple Updates
2024-12-25 03:02:24
  • Multiple Updates
2024-12-12 03:05:20
  • Multiple Updates
2024-11-23 03:02:24
  • Multiple Updates
2024-11-22 03:00:36
  • Multiple Updates
2024-11-20 02:58:56
  • Multiple Updates
2024-11-14 02:59:14
  • Multiple Updates
2024-11-09 02:59:15
  • Multiple Updates
2024-10-26 02:56:39
  • Multiple Updates
2024-10-25 02:58:34
  • Multiple Updates
2024-10-23 02:57:46
  • Multiple Updates
2024-10-03 02:53:05
  • Multiple Updates
2024-10-02 02:51:29
  • Multiple Updates
2024-09-15 02:49:11
  • Multiple Updates
2024-09-12 02:48:43
  • Multiple Updates
2024-09-07 02:47:43
  • Multiple Updates
2024-09-06 02:46:52
  • Multiple Updates
2024-09-04 02:50:05
  • Multiple Updates
2024-08-22 02:47:56
  • Multiple Updates
2024-08-08 21:27:34
  • Multiple Updates
2024-08-08 00:27:22
  • Multiple Updates
2024-08-07 21:27:25
  • First insertion