From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-58008: KEYS: trusted: dcp: fix improper sg use with CONFIG_VMAP_STACK=y
Date: Wed, 26 Feb 2025 18:11:02 -0800 [thread overview]
Message-ID: <2025022656-CVE-2024-58008-548d@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
KEYS: trusted: dcp: fix improper sg use with CONFIG_VMAP_STACK=y
With vmalloc stack addresses enabled (CONFIG_VMAP_STACK=y) DCP trusted
keys can crash during en- and decryption of the blob encryption key via
the DCP crypto driver. This is caused by improperly using sg_init_one()
with vmalloc'd stack buffers (plain_key_blob).
Fix this by always using kmalloc() for buffers we give to the DCP crypto
driver.
The Linux kernel CVE team has assigned CVE-2024-58008 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.11 with commit 0e28bf61a5f9ab30be3f3b4eafb8d097e39446bb and fixed in 6.12.14 with commit 3192f1c54dddb9b5820bf5e8677809949d8e9c66
Issue introduced in 6.11 with commit 0e28bf61a5f9ab30be3f3b4eafb8d097e39446bb and fixed in 6.13.3 with commit 3355594de46fb1cba663f12b9644b664b8a609f4
Issue introduced in 6.11 with commit 0e28bf61a5f9ab30be3f3b4eafb8d097e39446bb and fixed in 6.14-rc1 with commit e8d9fab39d1f87b52932646b2f1e7877aa3fc0f4
Issue introduced in 6.10.7 with commit 9e3b266afcfe4294e84496f50f006f029d3100db
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-58008
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:
security/keys/trusted-keys/trusted_dcp.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/3192f1c54dddb9b5820bf5e8677809949d8e9c66
https://git.kernel.org/stable/c/3355594de46fb1cba663f12b9644b664b8a609f4
https://git.kernel.org/stable/c/e8d9fab39d1f87b52932646b2f1e7877aa3fc0f4
reply other threads:[~2025-02-27 2:13 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=2025022656-CVE-2024-58008-548d@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.