test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QA Regression Testing |
Fix Released
|
Undecided
|
Unassigned | ||
ubuntu-kernel-tests |
Fix Released
|
Undecided
|
Po-Hsu Lin | ||
linux-kvm (Ubuntu) |
Fix Released
|
Undecided
|
Po-Hsu Lin | ||
Bionic |
Fix Released
|
Undecided
|
Po-Hsu Lin | ||
Cosmic |
Won't Fix
|
Undecided
|
Po-Hsu Lin | ||
Disco |
Fix Released
|
Undecided
|
Po-Hsu Lin |
Bug Description
== SRU Justification ==
Security team requires the CONFIG_
== Test ==
Test kernels could be found here:
https:/
This issue can be verified with test_410_
test from q-r-t, the test will pass with the patched kernel.
== Regression Potential ==
Low, we already have this config enabled in the generic kernel.
== Original bug report ==
Kernel Version: 4.15.0-44.47
This test has passed on s390x / AMD64 / ARM64 / i386, but failed with Power8 and Power9
FAIL: test_410_
Ensure kernel efi lockdown is enabled
-------
Traceback (most recent call last):
File "./test-
self.
File "./test-
self.
File "./test-
'%s option was expected to be set in the kernel config' % name)
AssertionError: LOCK_DOWN_KERNEL option was expected to be set in the kernel config
CVE References
tags: | added: bionic ppc64el |
description: | updated |
summary: |
test_410_config_lock_down_kernel in ubuntu_kernel_security test failed - on Bionic with PowerPC + on B/C KVM |
no longer affects: | linux (Ubuntu Bionic) |
no longer affects: | linux (Ubuntu Cosmic) |
summary: |
test_410_config_lock_down_kernel in ubuntu_kernel_security test failed - on B/C KVM + on B/C/D KVM |
Changed in ubuntu-kernel-tests: | |
status: | New → In Progress |
assignee: | nobody → Po-Hsu Lin (cypressyew) |
Changed in linux-kvm (Ubuntu): | |
assignee: | nobody → Po-Hsu Lin (cypressyew) |
Changed in linux-kvm (Ubuntu Bionic): | |
assignee: | nobody → Po-Hsu Lin (cypressyew) |
Changed in linux-kvm (Ubuntu Cosmic): | |
assignee: | nobody → Po-Hsu Lin (cypressyew) |
Changed in linux-kvm (Ubuntu Disco): | |
assignee: | nobody → Po-Hsu Lin (cypressyew) |
status: | New → In Progress |
Changed in linux-kvm (Ubuntu Cosmic): | |
status: | New → In Progress |
Changed in linux-kvm (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in linux-kvm (Ubuntu): | |
status: | New → In Progress |
description: | updated |
Changed in linux-kvm (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
Changed in linux-kvm (Ubuntu Cosmic): | |
status: | In Progress → Fix Committed |
Changed in linux-kvm (Ubuntu Disco): | |
status: | In Progress → Fix Committed |
tags: |
added: ubuntu-qrt-kernel-security removed: ubuntu-kernel-security |
Changed in ubuntu-kernel-tests: | |
status: | In Progress → Fix Released |
Changed in linux-kvm (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in linux-kvm (Ubuntu Cosmic): | |
status: | Fix Committed → Won't Fix |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1811981
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.