https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Sat, 09 May 2026 16:42:07 +0000 https://vulnerability.circl.lu/sighting/0ec95ee5-17be-4ddf-a87d-7b415a343ffa/export {"uuid": "0ec95ee5-17be-4ddf-a87d-7b415a343ffa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-38049", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12405", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-38049\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nx86/resctrl: Fix allocation of cleanest CLOSID on platforms with no monitors\n\nCommit\n\n 6eac36bb9eb0 (\"x86/resctrl: Allocate the cleanest CLOSID by searching closid_num_dirty_rmid\")\n\nadded logic that causes resctrl to search for the CLOSID with the fewest dirty\ncache lines when creating a new control group, if requested by the arch code.\nThis depends on the values read from the llc_occupancy counters. The logic is\napplicable to architectures where the CLOSID effectively forms part of the\nmonitoring identifier and so do not allow complete freedom to choose an unused\nmonitoring identifier for a given CLOSID.\n\nThis support missed that some platforms may not have these counters. This\ncauses a NULL pointer dereference when creating a new control group as the\narray was not allocated by dom_data_init().\n\nAs this feature isn't necessary on platforms that don't have cache occupancy\nmonitors, add this to the check that occurs when a new control group is\nallocated.\n\ud83d\udccf Published: 2025-04-18T07:01:30.421Z\n\ud83d\udccf Modified: 2025-04-18T07:01:30.421Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/a8a1bcc27d4607227088d80483164289b5348293\n2. https://git.kernel.org/stable/c/ed5addb55e403ad6598102bcf546e068ae01fef6\n3. https://git.kernel.org/stable/c/93a418fc61da13d1ee4047d4d1327990f7a2816a\n4. https://git.kernel.org/stable/c/a121798ae669351ec0697c94f71c3a692b2a755b", "creation_timestamp": "2025-04-18T07:59:21.000000Z"} {"uuid": "0ec95ee5-17be-4ddf-a87d-7b415a343ffa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-38049", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12405", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-38049\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nx86/resctrl: Fix allocation of cleanest CLOSID on platforms with no monitors\n\nCommit\n\n 6eac36bb9eb0 (\"x86/resctrl: Allocate the cleanest CLOSID by searching closid_num_dirty_rmid\")\n\nadded logic that causes resctrl to search for the CLOSID with the fewest dirty\ncache lines when creating a new control group, if requested by the arch code.\nThis depends on the values read from the llc_occupancy counters. The logic is\napplicable to architectures where the CLOSID effectively forms part of the\nmonitoring identifier and so do not allow complete freedom to choose an unused\nmonitoring identifier for a given CLOSID.\n\nThis support missed that some platforms may not have these counters. This\ncauses a NULL pointer dereference when creating a new control group as the\narray was not allocated by dom_data_init().\n\nAs this feature isn't necessary on platforms that don't have cache occupancy\nmonitors, add this to the check that occurs when a new control group is\nallocated.\n\ud83d\udccf Published: 2025-04-18T07:01:30.421Z\n\ud83d\udccf Modified: 2025-04-18T07:01:30.421Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/a8a1bcc27d4607227088d80483164289b5348293\n2. https://git.kernel.org/stable/c/ed5addb55e403ad6598102bcf546e068ae01fef6\n3. https://git.kernel.org/stable/c/93a418fc61da13d1ee4047d4d1327990f7a2816a\n4. https://git.kernel.org/stable/c/a121798ae669351ec0697c94f71c3a692b2a755b", "creation_timestamp": "2025-04-18T07:59:21.000000Z"} https://vulnerability.circl.lu/sighting/0ec95ee5-17be-4ddf-a87d-7b415a343ffa/export Fri, 18 Apr 2025 07:59:21 +0000