{"vulnerability": "CVE-2025-2184", "sightings": [{"uuid": "8218e265-a9a3-4fbd-9dcf-b9881f8f3c65", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21842", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ljrxr4vhzt22", "content": "", "creation_timestamp": "2025-03-07T12:04:57.125206Z"}, {"uuid": "38bd68a6-85dc-4461-9627-d2abb97795bd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21848", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-162-05", "content": "", "creation_timestamp": "2025-06-12T10:00:00.000000Z"}, {"uuid": "34d96194-5153-4565-be58-f72f31023321", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21840", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114120518037569175", "content": "", "creation_timestamp": "2025-03-07T09:48:33.703039Z"}, {"uuid": "09f3d77e-c928-4b37-8305-697383a060e4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21842", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/114120624260487340", "content": "", "creation_timestamp": "2025-03-07T10:15:45.957889Z"}, {"uuid": "9264806c-d626-46b6-b1d2-9e28e61b156f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-2184", "type": "seen", "source": "https://bsky.app/profile/getpokemon7.bsky.social/post/3lwpcalvyes2p", "content": "", "creation_timestamp": "2025-08-18T21:02:04.107861Z"}, {"uuid": "ba10dc7c-067e-4693-9716-fc11072ffe82", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-2184", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/115022455470697008", "content": "", "creation_timestamp": "2025-08-13T16:43:06.638680Z"}, {"uuid": "8cc02688-f75b-4d1f-af2a-09b40d58c823", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-2184", "type": "seen", "source": "https://security.paloaltonetworks.com/CVE-2025-2184", "content": "", "creation_timestamp": "2025-08-13T14:00:00.000000Z"}, {"uuid": "7e8f084f-0fba-409a-8a68-60a263c66cb6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-2184", "type": "seen", "source": "https://bsky.app/profile/ripjyr.bsky.social/post/3lwcjc5nt5c2k", "content": "", "creation_timestamp": "2025-08-13T19:03:34.844022Z"}, {"uuid": "bbde05dd-ffa3-4134-af3f-4600a8a3e900", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-2184", "type": "seen", "source": "https://bsky.app/profile/secqube.com/post/3mguhif77q327", "content": "", "creation_timestamp": "2026-03-12T13:02:18.640642Z"}, {"uuid": "3acad6f5-1718-497f-8348-68d784fae2db", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21843", "type": "seen", "source": "https://t.me/cvedetector/19809", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21843 - Linux Kernel Panthor Uninitialized Data Use\", \n  \"Content\": \"CVE ID : CVE-2025-21843 \nPublished : March 7, 2025, 9:15 a.m. | 1\u00a0hour, 46\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/panthor: avoid garbage value in panthor_ioctl_dev_query()  \n  \n'priorities_info' is uninitialized, and the uninitialized value is copied  \nto user object when calling PANTHOR_UOBJ_SET(). Using memset to initialize  \n'priorities_info' to avoid this garbage value problem. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"07 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-07T12:25:47.000000Z"}, {"uuid": "ed3eb197-a951-4688-a44b-19c5b5f04375", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21842", "type": "seen", "source": "https://t.me/cvedetector/19808", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21842 - AMD KFD Use-After-Free Buffer Overflow\", \n  \"Content\": \"CVE ID : CVE-2025-21842 \nPublished : March 7, 2025, 9:15 a.m. | 1\u00a0hour, 46\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \namdkfd: properly free gang_ctx_bo when failed to init user queue  \n  \nThe destructor of a gtt bo is declared as  \nvoid amdgpu_amdkfd_free_gtt_mem(struct amdgpu_device *adev, void **mem_obj);  \nWhich takes void** as the second parameter.  \n  \nGCC allows passing void* to the function because void* can be implicitly  \ncasted to any other types, so it can pass compiling.  \n  \nHowever, passing this void* parameter into the function's  \nexecution process(which expects void** and dereferencing void**)  \nwill result in errors. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"07 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-07T12:25:47.000000Z"}, {"uuid": "4f0e6cc1-fba8-49cb-818a-b3d90ceaade1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21841", "type": "seen", "source": "https://t.me/cvedetector/19807", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21841 - AMD P-State Kernel Reference Counting Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21841 \nPublished : March 7, 2025, 9:15 a.m. | 1\u00a0hour, 46\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ncpufreq/amd-pstate: Fix cpufreq_policy ref counting  \n  \namd_pstate_update_limits() takes a cpufreq_policy reference but doesn't  \ndecrement the refcount in one of the exit paths, fix that. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"07 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-07T12:25:46.000000Z"}, {"uuid": "c82c8754-81ff-4af2-9109-c24906265d82", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-21840", "type": "seen", "source": "https://t.me/cvedetector/19806", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21840 - Intel LPMD Thermal Netlink Integer Underflow Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21840 \nPublished : March 7, 2025, 9:15 a.m. | 1\u00a0hour, 46\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nthermal/netlink: Prevent userspace segmentation fault by adjusting UAPI header  \n  \nThe intel-lpmd tool [1], which uses the THERMAL_GENL_ATTR_CPU_CAPABILITY  \nattribute to receive HFI events from kernel space, encounters a  \nsegmentation fault after commit 1773572863c4 (\"thermal: netlink: Add the  \ncommands and the events for the thresholds\").  \n  \nThe issue arises because the THERMAL_GENL_ATTR_CPU_CAPABILITY raw value  \nwas changed while intel_lpmd still uses the old value.  \n  \nAlthough intel_lpmd can be updated to check the THERMAL_GENL_VERSION and  \nuse the appropriate THERMAL_GENL_ATTR_CPU_CAPABILITY value, the commit  \nitself is questionable.  \n  \nThe commit introduced a new element in the middle of enum thermal_genl_attr,  \nwhich affects many existing attributes and introduces potential risks  \nand unnecessary maintenance burdens for userspace thermal netlink event  \nusers.  \n  \nSolve the issue by moving the newly introduced  \nTHERMAL_GENL_ATTR_TZ_PREV_TEMP attribute to the end of the  \nenum thermal_genl_attr. This ensures that all existing thermal generic  \nnetlink attributes remain unaffected.  \n  \n[ rjw: Subject edits ] \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"07 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-07T12:25:45.000000Z"}]}