{"vulnerability": "CVE-2024-57849", "sightings": [{"uuid": "23ef8d8f-04e8-4416-afaa-d717204c0467", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57849", "type": "seen", "source": "https://t.me/cvedetector/15091", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57849 - \"IBM s390 cpu hotplug sample buffer use after free vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-57849 \nPublished : Jan. 11, 2025, 3:15 p.m. | 42\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ns390/cpum_sf: Handle CPU hotplug remove during sampling  \n  \nCPU hotplug remove handling triggers the following function  \ncall sequence:  \n  \n   CPUHP_AP_PERF_S390_SF_ONLINE  --> s390_pmu_sf_offline_cpu()  \n   ...  \n   CPUHP_AP_PERF_ONLINE          --> perf_event_exit_cpu()  \n  \nThe s390 CPUMF sampling CPU hotplug handler invokes:  \n  \n s390_pmu_sf_offline_cpu()  \n +-->  cpusf_pmu_setup()  \n       +--> setup_pmc_cpu()  \n            +--> deallocate_buffers()  \n  \nThis function de-allocates all sampling data buffers (SDBs) allocated  \nfor that CPU at event initialization. It also clears the  \nPMU_F_RESERVED bit. The CPU is gone and can not be sampled.  \n  \nWith the event still being active on the removed CPU, the CPU event  \nhotplug support in kernel performance subsystem triggers the  \nfollowing function calls on the removed CPU:  \n  \n  perf_event_exit_cpu()  \n  +--> perf_event_exit_cpu_context()  \n       +--> __perf_event_exit_context()  \n     +--> __perf_remove_from_context()  \n          +--> event_sched_out()  \n               +--> cpumsf_pmu_del()  \n                    +--> cpumsf_pmu_stop()  \n                                +--> hw_perf_event_update()  \n  \nto stop and remove the event. During removal of the event, the  \nsampling device driver tries to read out the remaining samples from  \nthe sample data buffers (SDBs). But they have already been freed  \n(and may have been re-assigned). This may lead to a use after free  \nsituation in which case the samples are most likely invalid. In the  \nbest case the memory has not been reassigned and still contains  \nvalid data.  \n  \nRemedy this situation and check if the CPU is still in reserved  \nstate (bit PMU_F_RESERVED set). In this case the SDBs have not been  \nreleased an contain valid data. This is always the case when  \nthe event is removed (and no CPU hotplug off occured).  \nIf the PMU_F_RESERVED bit is not set, the SDB buffers are gone. \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:39.000000Z"}, {"uuid": "9ca90883-9f0a-413f-9a60-1a1049ced024", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57849", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113810229085340766", "content": "", "creation_timestamp": "2025-01-11T14:37:59.423853Z"}, {"uuid": "328f17c5-68ca-4f98-913e-63d0e985f1f2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57849", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfhyrbyyml2i", "content": "", "creation_timestamp": "2025-01-11T15:15:30.328779Z"}, {"uuid": "693d8b15-f1bc-447b-aea4-a2affee502bd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57849", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/1329", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-57849\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ns390/cpum_sf: Handle CPU hotplug remove during sampling\n\nCPU hotplug remove handling triggers the following function\ncall sequence:\n\n   CPUHP_AP_PERF_S390_SF_ONLINE  --> s390_pmu_sf_offline_cpu()\n   ...\n   CPUHP_AP_PERF_ONLINE          --> perf_event_exit_cpu()\n\nThe s390 CPUMF sampling CPU hotplug handler invokes:\n\n s390_pmu_sf_offline_cpu()\n +-->  cpusf_pmu_setup()\n       +--> setup_pmc_cpu()\n            +--> deallocate_buffers()\n\nThis function de-allocates all sampling data buffers (SDBs) allocated\nfor that CPU at event initialization. It also clears the\nPMU_F_RESERVED bit. The CPU is gone and can not be sampled.\n\nWith the event still being active on the removed CPU, the CPU event\nhotplug support in kernel performance subsystem triggers the\nfollowing function calls on the removed CPU:\n\n  perf_event_exit_cpu()\n  +--> perf_event_exit_cpu_context()\n       +--> __perf_event_exit_context()\n     +--> __perf_remove_from_context()\n          +--> event_sched_out()\n               +--> cpumsf_pmu_del()\n                    +--> cpumsf_pmu_stop()\n                                +--> hw_perf_event_update()\n\nto stop and remove the event. During removal of the event, the\nsampling device driver tries to read out the remaining samples from\nthe sample data buffers (SDBs). But they have already been freed\n(and may have been re-assigned). This may lead to a use after free\nsituation in which case the samples are most likely invalid. In the\nbest case the memory has not been reassigned and still contains\nvalid data.\n\nRemedy this situation and check if the CPU is still in reserved\nstate (bit PMU_F_RESERVED set). In this case the SDBs have not been\nreleased an contain valid data. This is always the case when\nthe event is removed (and no CPU hotplug off occured).\nIf the PMU_F_RESERVED bit is not set, the SDB buffers are gone.\n\ud83d\udccf Published: 2025-01-11T14:30:58.365Z\n\ud83d\udccf Modified: 2025-01-11T14:30:58.365Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/238e3af849dfdcb1faed544349f7025e533f9aab\n2. https://git.kernel.org/stable/c/99192c735ed4bfdff0d215ec85c8a87a677cb898\n3. https://git.kernel.org/stable/c/06a92f810df8037ca36157282ddcbefdcaf049b8\n4. https://git.kernel.org/stable/c/b5be6a0bb639d165c8418d8dddd8f322587be8be\n5. https://git.kernel.org/stable/c/a69752f1e5de817941a2ea0609254f6f25acd274\n6. https://git.kernel.org/stable/c/be54e6e0f93a39a9c00478d70d12956a5f3d5b9b\n7. https://git.kernel.org/stable/c/a0bd7dacbd51c632b8e2c0500b479af564afadf3", "creation_timestamp": "2025-01-11T15:05:21.000000Z"}]}