Metrics
Affected Vendors & Products
Mon, 24 Mar 2025 19:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Linux
Linux linux Kernel |
|
CPEs | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | |
Vendors & Products |
Linux
Linux linux Kernel |
Tue, 04 Mar 2025 03:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Thu, 27 Feb 2025 18:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-416 | |
Metrics |
cvssV3_1
|
cvssV3_1
|
Thu, 27 Feb 2025 13:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Thu, 27 Feb 2025 02:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | 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. | |
Title | drm/xe/tracing: Fix a potential TP_printk UAF | |
References |
|

Status: PUBLISHED
Assigner: Linux
Published: 2025-02-27T02:18:06.123Z
Updated: 2025-03-24T15:37:08.719Z
Reserved: 2025-02-27T02:16:34.083Z
Link: CVE-2024-49570

Updated: 2025-02-27T17:57:56.874Z

Status : Analyzed
Published: 2025-02-27T03:15:10.267
Modified: 2025-03-24T18:56:21.257
Link: CVE-2024-49570
