{"uuid": "127bffd4-e2b3-4952-b4a4-60ec18e74223", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57839", "type": "seen", "source": "https://t.me/cvedetector/15096", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57839 - NFS Linux Kernel Readahead Hang Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57839 \nPublished : Jan. 11, 2025, 3:15 p.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nRevert \"readahead: properly shorten readahead when falling back to do_page_cache_ra()\"  \n  \nThis reverts commit 7c877586da3178974a8a94577b6045a48377ff25.  \n  \nAnders and Philippe have reported that recent kernels occasionally hang  \nwhen used with NFS in readahead code.  The problem has been bisected to  \n7c877586da3 (\"readahead: properly shorten readahead when falling back to  \ndo_page_cache_ra()\").  The cause of the problem is that ra->size can be  \nshrunk by read_pages() call and subsequently we end up calling  \ndo_page_cache_ra() with negative (read huge positive) number of pages.   \nLet's revert 7c877586da3 for now until we can find a proper way how the  \nlogic in read_pages() and page_cache_ra_order() can coexist.  This can  \nlead to reduced readahead throughput due to readahead window confusion but  \nthat's better than outright hangs. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"11 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-11T17:26:46.000000Z"}