{"vulnerability": "CVE-2024-57892", "sightings": [{"uuid": "85cada19-7bf7-4cfb-8107-ee4e9386ecf1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57892", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfrtyvorop2n", "content": "", "creation_timestamp": "2025-01-15T13:16:54.064483Z"}, {"uuid": "2d98289e-52e7-4c90-af0a-5cfe6e8a9555", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57892", "type": "seen", "source": "https://t.me/cvedetector/15459", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57892 - Linux Kernel Ocfs2 Slab-Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57892 \nPublished : Jan. 15, 2025, 1:15 p.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nocfs2: fix slab-use-after-free due to dangling pointer dqi_priv  \n  \nWhen mounting ocfs2 and then remounting it as read-only, a  \nslab-use-after-free occurs after the user uses a syscall to  \nquota_getnextquota.  Specifically, sb_dqinfo(sb, type)->dqi_priv is the  \ndangling pointer.  \n  \nDuring the remounting process, the pointer dqi_priv is freed but is never  \nset as null leaving it to be accessed.  Additionally, the read-only option  \nfor remounting sets the DQUOT_SUSPENDED flag instead of setting the  \nDQUOT_USAGE_ENABLED flags.  Moreover, later in the process of getting the  \nnext quota, the function ocfs2_get_next_id is called and only checks the  \nquota usage flags and not the quota suspended flags.  \n  \nTo fix this, I set dqi_priv to null when it is freed after remounting with  \nread-only and put a check for DQUOT_SUSPENDED in ocfs2_get_next_id.  \n  \n[akpm@linux-foundation.org: coding-style cleanups] \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"15 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-15T15:07:05.000000Z"}, {"uuid": "ac8f5a4b-c5f9-416a-a6b0-bf5e9793fca8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-57892", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/1755", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-57892\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: fix slab-use-after-free due to dangling pointer dqi_priv\n\nWhen mounting ocfs2 and then remounting it as read-only, a\nslab-use-after-free occurs after the user uses a syscall to\nquota_getnextquota.  Specifically, sb_dqinfo(sb, type)->dqi_priv is the\ndangling pointer.\n\nDuring the remounting process, the pointer dqi_priv is freed but is never\nset as null leaving it to be accessed.  Additionally, the read-only option\nfor remounting sets the DQUOT_SUSPENDED flag instead of setting the\nDQUOT_USAGE_ENABLED flags.  Moreover, later in the process of getting the\nnext quota, the function ocfs2_get_next_id is called and only checks the\nquota usage flags and not the quota suspended flags.\n\nTo fix this, I set dqi_priv to null when it is freed after remounting with\nread-only and put a check for DQUOT_SUSPENDED in ocfs2_get_next_id.\n\n[akpm@linux-foundation.org: coding-style cleanups]\n\ud83d\udccf Published: 2025-01-15T13:05:44.635Z\n\ud83d\udccf Modified: 2025-01-15T13:05:44.635Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/2e3d203b1adede46bbba049e497765d67865be18\n2. https://git.kernel.org/stable/c/ba950a02d8d23811aa1120affd3adedcfac6153d\n3. https://git.kernel.org/stable/c/5f3fd772d152229d94602bca243fbb658068a597", "creation_timestamp": "2025-01-15T14:25:31.000000Z"}]}