{"vulnerability": "CVE-2024-57838", "sightings": [{"uuid": "d024aa53-2939-459f-b2c7-7fefc2a28a77", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57838", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "e3cc2e4f-a3ac-435b-a08c-c63fb48365ac", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57838", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/1332", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2024-57838\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ns390/entry: Mark IRQ entries to fix stack depot warnings\n\nThe stack depot filters out everything outside of the top interrupt\ncontext as an uninteresting or irrelevant part of the stack traces. This\nhelps with stack trace de-duplication, avoiding an explosion of saved\nstack traces that share the same IRQ context code path but originate\nfrom different randomly interrupted points, eventually exhausting the\nstack depot.\n\nFiltering uses in_irqentry_text() to identify functions within the\n.irqentry.text and .softirqentry.text sections, which then become the\nlast stack trace entries being saved.\n\nWhile __do_softirq() is placed into the .softirqentry.text section by\ncommon code, populating .irqentry.text is architecture-specific.\n\nCurrently, the .irqentry.text section on s390 is empty, which prevents\nstack depot filtering and de-duplication and could result in warnings\nlike:\n\nStack depot reached limit capacity\nWARNING: CPU: 0 PID: 286113 at lib/stackdepot.c:252 depot_alloc_stack+0x39a/0x3c8\n\nwith PREEMPT and KASAN enabled.\n\nFix this by moving the IO/EXT interrupt handlers from .kprobes.text into\nthe .irqentry.text section and updating the kprobes blacklist to include\nthe .irqentry.text section.\n\nThis is done only for asynchronous interrupts and explicitly not for\nprogram checks, which are synchronous and where the context beyond the\nprogram check is important to preserve. Despite machine checks being\nsomewhat in between, they are extremely rare, and preserving context\nwhen possible is also of value.\n\nSVCs and Restart Interrupts are not relevant, one being always at the\nboundary to user space and the other being a one-time thing.\n\nIRQ entries filtering is also optionally used in ftrace function graph,\nwhere the same logic applies.\n\ud83d\udccf Published: 2025-01-11T14:08:56.951Z\n\ud83d\udccf Modified: 2025-01-11T14:08:56.951Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/ca687fdce5b95f84d91d6e36ac77047771eb3dfc\n2. https://git.kernel.org/stable/c/5bb7a2c3afcf8732dc65ea49c09147b07da1d993\n3. https://git.kernel.org/stable/c/1af22528fee8072b7adc007b8ca49cc4ea62689e\n4. https://git.kernel.org/stable/c/473ffae3030188f1c6b80e1b3631a26b4adf7b32\n5. https://git.kernel.org/stable/c/45c9f2b856a075a34873d00788d2e8a250c1effd", "creation_timestamp": "2025-01-11T15:05:28.000000Z"}, {"uuid": "16269a14-68b2-4102-9e02-2af0e6d0bff6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57838", "type": "seen", "source": "https://t.me/cvedetector/15080", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57838 - IBM zSeries s390 Linux Kernel Stack Depot Stack Overflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-57838 \nPublished : Jan. 11, 2025, 2:15 p.m. | 25\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ns390/entry: Mark IRQ entries to fix stack depot warnings  \n  \nThe stack depot filters out everything outside of the top interrupt  \ncontext as an uninteresting or irrelevant part of the stack traces. This  \nhelps with stack trace de-duplication, avoiding an explosion of saved  \nstack traces that share the same IRQ context code path but originate  \nfrom different randomly interrupted points, eventually exhausting the  \nstack depot.  \n  \nFiltering uses in_irqentry_text() to identify functions within the  \n.irqentry.text and .softirqentry.text sections, which then become the  \nlast stack trace entries being saved.  \n  \nWhile __do_softirq() is placed into the .softirqentry.text section by  \ncommon code, populating .irqentry.text is architecture-specific.  \n  \nCurrently, the .irqentry.text section on s390 is empty, which prevents  \nstack depot filtering and de-duplication and could result in warnings  \nlike:  \n  \nStack depot reached limit capacity  \nWARNING: CPU: 0 PID: 286113 at lib/stackdepot.c:252 depot_alloc_stack+0x39a/0x3c8  \n  \nwith PREEMPT and KASAN enabled.  \n  \nFix this by moving the IO/EXT interrupt handlers from .kprobes.text into  \nthe .irqentry.text section and updating the kprobes blacklist to include  \nthe .irqentry.text section.  \n  \nThis is done only for asynchronous interrupts and explicitly not for  \nprogram checks, which are synchronous and where the context beyond the  \nprogram check is important to preserve. Despite machine checks being  \nsomewhat in between, they are extremely rare, and preserving context  \nwhen possible is also of value.  \n  \nSVCs and Restart Interrupts are not relevant, one being always at the  \nboundary to user space and the other being a one-time thing.  \n  \nIRQ entries filtering is also optionally used in ftrace function graph,  \nwhere the same logic applies. \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-11T15:46:15.000000Z"}, {"uuid": "0358882d-d01c-4ee8-8ff1-a2cc2cebc999", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57838", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113810135114718803", "content": "", "creation_timestamp": "2025-01-11T14:14:06.054828Z"}, {"uuid": "887ba802-d4bc-4a11-bc09-6a26df1a765b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57838", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lfhvgdn3wc2f", "content": "", "creation_timestamp": "2025-01-11T14:15:41.249200Z"}, {"uuid": "c61ffa85-6aec-435f-aae7-885d53be10db", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57838", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lfhwxvrrdv2e", "content": "", "creation_timestamp": "2025-01-11T14:43:25.045937Z"}]}