Bug 2348556 (CVE-2024-49570) - CVE-2024-49570 kernel: drm/xe/tracing: Fix a potential TP_printk UAF
Summary: CVE-2024-49570 kernel: drm/xe/tracing: Fix a potential TP_printk UAF
Keywords:
Status: NEW
Alias: CVE-2024-49570
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-27 03:03 UTC by OSIDB Bzimport
Modified: 2025-11-11 10:25 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2025:20095 0 None None None 2025-11-11 08:02:10 UTC
Red Hat Product Errata RHSA-2025:20518 0 None None None 2025-11-11 10:25:26 UTC

Description OSIDB Bzimport 2025-02-27 03:03:09 UTC
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.

Comment 2 errata-xmlrpc 2025-11-11 08:02:09 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2025:20095 https://access.redhat.com/errata/RHSA-2025:20095

Comment 3 errata-xmlrpc 2025-11-11 10:25:25 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2025:20518 https://access.redhat.com/errata/RHSA-2025:20518


Note You need to log in before you can comment on or make changes to this bug.