From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-27406: lib/Kconfig.debug: TEST_IOV_ITER depends on MMU
Date: Fri, 17 May 2024 13:40:41 +0200 [thread overview]
Message-ID: <2024051739-CVE-2024-27406-cfc3@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
lib/Kconfig.debug: TEST_IOV_ITER depends on MMU
Trying to run the iov_iter unit test on a nommu system such as the qemu
kc705-nommu emulation results in a crash.
KTAP version 1
# Subtest: iov_iter
# module: kunit_iov_iter
1..9
BUG: failure at mm/nommu.c:318/vmap()!
Kernel panic - not syncing: BUG!
The test calls vmap() directly, but vmap() is not supported on nommu
systems, causing the crash. TEST_IOV_ITER therefore needs to depend on
MMU.
The Linux kernel CVE team has assigned CVE-2024-27406 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.6 with commit 2d71340ff1d4 and fixed in 6.6.19 with commit e6316749d603
Issue introduced in 6.6 with commit 2d71340ff1d4 and fixed in 6.7.7 with commit 9e6e541b9776
Issue introduced in 6.6 with commit 2d71340ff1d4 and fixed in 6.8 with commit 1eb1e984379e
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-27406
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:
lib/Kconfig.debug
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/e6316749d603fe9c4c91f6ec3694e06e4de632a3
https://git.kernel.org/stable/c/9e6e541b97762d5b1143070067f7c68f39a408f8
https://git.kernel.org/stable/c/1eb1e984379e2da04361763f66eec90dd75cf63e
next reply other threads:[~2024-05-17 11:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 11:40 Greg Kroah-Hartman [this message]
2024-05-17 17:42 ` CVE-2024-27406: lib/Kconfig.debug: TEST_IOV_ITER depends on MMU Michal Koutný
2024-05-19 8:53 ` Greg Kroah-Hartman
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=2024051739-CVE-2024-27406-cfc3@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.