From: Lee Jones <lee@kernel.org>
To: linux-cve-announce@vger.kernel.org
Cc: Lee Jones <lee@kernel.org>
Subject: CVE-2024-26649: drm/amdgpu: Fix the null pointer when load rlc firmware
Date: Tue, 26 Mar 2024 17:50:15 +0000 [thread overview]
Message-ID: <20240326175007.1388794-17-lee@kernel.org> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: Fix the null pointer when load rlc firmware
If the RLC firmware is invalid because of wrong header size,
the pointer to the rlc firmware is released in function
amdgpu_ucode_request. There will be a null pointer error
in subsequent use. So skip validation to fix it.
The Linux kernel CVE team has assigned CVE-2024-26649 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.3 with commit 3da9b71563cb and fixed in 6.6.15 with commit 8b5bacce2d13
Issue introduced in 6.3 with commit 3da9b71563cb and fixed in 6.7.3 with commit d3887448486c
Issue introduced in 6.3 with commit 3da9b71563cb and fixed in 6.8 with commit bc03c02cc199
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-26649
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/amd/amdgpu/gfx_v10_0.c
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/8b5bacce2d13dbe648f0bfd3f738ecce8db4978c
https://git.kernel.org/stable/c/d3887448486caeef9687fb5dfebd4ff91e0f25aa
https://git.kernel.org/stable/c/bc03c02cc1991a066b23e69bbcc0f66e8f1f7453
reply other threads:[~2024-03-26 17:50 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=20240326175007.1388794-17-lee@kernel.org \
--to=lee@kernel.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.