{"uuid": "3f0ba274-b717-4935-9a19-45514af3dae3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-53131", "type": "seen", "source": "https://t.me/cvedetector/11994", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-53131 - In the Linux kernel, the following vulnerability h\", \n  \"Content\": \"CVE ID : CVE-2024-53131 \nPublished : Dec. 4, 2024, 3:15 p.m. | 18\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnilfs2: fix null-ptr-deref in block_touch_buffer tracepoint  \n  \nPatch series \"nilfs2: fix null-ptr-deref bugs on block tracepoints\".  \n  \nThis series fixes null pointer dereference bugs that occur when using  \nnilfs2 and two block-related tracepoints.  \n  \n  \nThis patch (of 2):  \n  \nIt has been reported that when using \"block:block_touch_buffer\"  \ntracepoint, touch_buffer() called from __nilfs_get_folio_block() causes a  \nNULL pointer dereference, or a general protection fault when KASAN is  \nenabled.  \n  \nThis happens because since the tracepoint was added in touch_buffer(), it  \nreferences the dev_t member bh->b_bdev->bd_dev regardless of whether the  \nbuffer head has a pointer to a block_device structure.  In the current  \nimplementation, the block_device structure is set after the function  \nreturns to the caller.  \n  \nHere, touch_buffer() is used to mark the folio/page that owns the buffer  \nhead as accessed, but the common search helper for folio/page used by the  \ncaller function was optimized to mark the folio/page as accessed when it  \nwas reimplemented a long time ago, eliminating the need to call  \ntouch_buffer() here in the first place.  \n  \nSo this solves the issue by eliminating the touch_buffer() call itself. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"04 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-04T16:45:27.000000Z"}