From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-49570: drm/xe/tracing: Fix a potential TP_printk UAF
Date: Wed, 26 Feb 2025 18:17:01 -0800 [thread overview]
Message-ID: <2025022601-CVE-2024-49570-d2e7@gregkh> (raw)
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.
The Linux kernel CVE team has assigned CVE-2024-49570 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.11 with commit e46d3f813abd2383881c66d21ba04cee9fbdf3a9 and fixed in 6.12.16 with commit 62cd174616ae3bf8a6cf468718f1ae74e5a07727
Issue introduced in 6.11 with commit e46d3f813abd2383881c66d21ba04cee9fbdf3a9 and fixed in 6.13.4 with commit c9402da34611e1039ecccba3c1481c4866f7ca64
Issue introduced in 6.11 with commit e46d3f813abd2383881c66d21ba04cee9fbdf3a9 and fixed in 6.14-rc1 with commit 07089083a526ea19daa72a1edf9d6e209615b77c
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2024-49570
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/gpu/drm/xe/xe_trace_bo.h
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/62cd174616ae3bf8a6cf468718f1ae74e5a07727
https://git.kernel.org/stable/c/c9402da34611e1039ecccba3c1481c4866f7ca64
https://git.kernel.org/stable/c/07089083a526ea19daa72a1edf9d6e209615b77c
reply other threads:[~2025-02-27 2:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025022601-CVE-2024-49570-d2e7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.