CVE-2024-36882: mm: use memalloc_nofs_save() in page_cache_ra_order()
In the Linux kernel, the following vulnerability has been resolved:
mm: use memalloc_nofs_save() in page_cache_ra_order()
See commit f2c817bed58d ("mm: use memalloc_nofs_save in readahead path"),
ensure that page_cache_ra_order() do not attempt to reclaim file-backed
pages too, or it leads to a deadlock, found issue when test ext4 large
folio.
INFO: task DataXceiver for:7494 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:DataXceiver for state:D stack:0 pid:7494 ppid:1 flags:0x00000200
Call trace:
__switch_to+0x14c/0x240
__schedule+0x82c/0xdd0
schedule+0x58/0xf0
io_schedule+0x24/0xa0
__folio_lock+0x130/0x300
migrate_pages_batch+0x378/0x918
migrate_pages+0x350/0x700
compact_zone+0x63c/0xb38
compact_zone_order+0xc0/0x118
try_to_compact_pages+0xb0/0x280
__alloc_pages_direct_compact+0x98/0x248
__alloc_pages+0x510/0x1110
alloc_pages+0x9c/0x130
folio_alloc+0x20/0x78
filemap_alloc_folio+0x8c/0x1b0
page_cache_ra_order+0x174/0x308
ondemand_readahead+0x1c8/0x2b8
page_cache_async_ra+0x68/0xb8
filemap_readahead.isra.0+0x64/0xa8
filemap_get_pages+0x3fc/0x5b0
filemap_splice_read+0xf4/0x280
ext4_file_splice_read+0x2c/0x48 [ext4]
vfs_splice_read.part.0+0xa8/0x118
splice_direct_to_actor+0xbc/0x288
do_splice_direct+0x9c/0x108
do_sendfile+0x328/0x468
__arm64_sys_sendfile64+0x8c/0x148
invoke_syscall+0x4c/0x118
el0_svc_common.constprop.0+0xc8/0xf0
do_el0_svc+0x24/0x38
el0_svc+0x4c/0x1f8
el0t_64_sync_handler+0xc0/0xc8
el0t_64_sync+0x188/0x190
Security readout for executives and security teams
Plain-English summary
CVE-2024-36882 is a Linux kernel memory-management bug that can cause blocked tasks or a deadlock during file readahead. The provided trace shows the issue in an ext4 large-folio test path using sendfile. The business impact is availability risk on affected Linux systems, not confirmed data theft or privilege escalation.
Executive priority
Track this as an availability reliability fix for Linux estates. Prioritize exposed production systems with high file I/O, but do not treat it as confirmed exploited based on the supplied evidence.
Technical view
The fix wraps page_cache_ra_order() allocation behavior with memalloc_nofs_save() so the readahead path does not reclaim file-backed pages and deadlock. The source references prior readahead NOFS handling and shows a blocked DataXceiver task in ext4_file_splice_read through filemap readahead and page allocation/compaction.
Likely exposure
Exposure is limited to Linux kernels covered by the affected metadata, including kernel lines around 5.18 and fixed stable references for 6.1.91, 6.6.31, 6.8.10, and 6.9. Distro backports may change package-level exposure.
Exploitation context
The source bundle does not claim active exploitation, public exploit availability, or remote triggerability. CISA KEV status is false. Evidence supports a kernel deadlock condition observed during testing with ext4 large folios, file readahead, and sendfile-style file transfer behavior.
Researcher notes
The record lacks CVSS, CWE, and exploitability detail. Key validation work is version-range interpretation and downstream distro backport mapping. Avoid assuming impact beyond deadlock or hung-task availability without additional vendor evidence.
Mitigation direction
Update affected Linux kernels using vendor or distribution guidance.
Map running kernel packages to the referenced stable fix commits.
Prioritize systems with heavy file serving, ext4, or sendfile workloads.
Check vendor advisories before applying assumptions from upstream version numbers.
Validation and detection
Inventory Linux kernel versions across servers and appliances.
Confirm whether distro kernels include the referenced upstream fixes.
Review kernel logs for hung tasks or blocked file I/O traces.
Test representative file-serving workloads after kernel updates.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-36882 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.