{"uuid": "601919cf-2526-40dd-8ecb-53aa51559afe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57927", "type": "seen", "source": "https://t.me/cvedetector/15851", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57927 - Linux Kernel NFS Null File Pointer Cahce Writing Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57927 \nPublished : Jan. 19, 2025, 12:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnfs: Fix oops in nfs_netfs_init_request() when copying to cache  \n  \nWhen netfslib wants to copy some data that has just been read on behalf of  \nnfs, it creates a new write request and calls nfs_netfs_init_request() to  \ninitialise it, but with a NULL file pointer.  This causes  \nnfs_file_open_context() to oops - however, we don't actually need the nfs  \ncontext as we're only going to write to the cache.  \n  \nFix this by just returning if we aren't given a file pointer and emit a  \nwarning if the request was for something other than copy-to-cache.  \n  \nFurther, fix nfs_netfs_free_request() so that it doesn't try to free the  \ncontext if the pointer is NULL. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-19T13:58:25.000000Z"}