lib/Kconfig.debug: TEST_IOV_ITER depends on MMU
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.6.196.7.76.8In 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.
From the CVE record · Linux
The Linux kernel’s iov_iter unit test calls vmap(), which is unsupported on systems without an MMU. Running the test on such a system can cause a kernel panic. The input does not describe an attacker or exploitation conditions.
Engineers running the Linux kernel’s TEST_IOV_ITER test on systems without an MMU should check their configuration; affected versions are not specified.