{"vulnerability": "CVE-2024-42079", "sightings": [{"uuid": "252d892c-5f2b-4d43-be2a-4deb5c954a55", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-42079", "type": "seen", "source": "https://t.me/cvedetector/1876", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42079 - \"Linux GFS2 NULL Pointer Dereference Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-42079 \nPublished : July 29, 2024, 4:15 p.m. | 26\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ngfs2: Fix NULL pointer dereference in gfs2_log_flush  \n  \nIn gfs2_jindex_free(), set sdp-&gt;sd_jdesc to NULL under the log flush  \nlock to provide exclusion against gfs2_log_flush().  \n  \nIn gfs2_log_flush(), check if sdp-&gt;sd_jdesc is non-NULL before  \ndereferencing it.  Otherwise, we could run into a NULL pointer  \ndereference when outstanding glock work races with an unmount  \n(glock_work_func -&gt; run_queue -&gt; do_xmote -&gt; inode_go_sync -&gt;  \ngfs2_log_flush). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-29T18:48:28.000000Z"}, {"uuid": "e1ddf20d-b96c-4574-b723-1ee71a713b47", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-42079", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}]}