Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2024-49570 | First vendor Publication | 2025-02-27 |
| Vendor | Cve | Last vendor Modification | 2025-03-24 |
Security-Database Scoring CVSS v3
| Cvss vector : N/A | |||
|---|---|---|---|
| Overall CVSS Score | NA | ||
| Base Score | NA | Environmental Score | NA |
| impact SubScore | NA | Temporal Score | NA |
| Exploitabality Sub Score | NA | ||
| Calculate full CVSS 3.0 Vectors scores | |||
Security-Database Scoring CVSS v2
| Cvss vector : | |||
|---|---|---|---|
| Cvss Base Score | N/A | Attack Range | N/A |
| Cvss Impact Score | N/A | Attack Complexity | N/A |
| Cvss Expoit Score | N/A | Authentication | N/A |
| Calculate full CVSS 2.0 Vectors scores | |||
Detail
| In the Linux kernel, the following vulnerability has been resolved: drm/xe/tracing: Fix a potential TP_printk UAF The commit afd2627f727b ("tracing: Check "%s" dereference via the field and not the TP_printk format") exposes potential UAFs in the xe_bo_move trace event. Fix those by avoiding dereferencing the xe_mem_type_to_name[] array at TP_printk time. Since some code refactoring has taken place, explicit backporting may be needed for kernels older than 6.10. |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49570 |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2025-03-28 17:20:54 |
|
| 2025-03-28 13:45:40 |
|
| 2025-03-28 03:19:30 |
|
| 2025-03-25 03:30:35 |
|
| 2025-03-25 00:20:47 |
|
| 2025-02-28 03:46:08 |
|
| 2025-02-28 03:43:46 |
|
| 2025-02-27 21:20:33 |
|
| 2025-02-27 09:20:32 |
|
