| 2018-04-25 04:36:07 |
Po-Hsu Lin |
bug |
|
|
added bug |
| 2018-04-25 04:36:29 |
Po-Hsu Lin |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-04-25 04:36:45 |
Po-Hsu Lin |
bug task added |
|
qa-regression-testing |
|
| 2018-06-01 12:08:54 |
Po-Hsu Lin |
bug task added |
|
ubuntu-kernel-tests |
|
| 2018-06-12 10:32:53 |
Po-Hsu Lin |
bug task deleted |
qa-regression-testing |
|
|
| 2018-06-12 10:32:57 |
Po-Hsu Lin |
ubuntu-kernel-tests: assignee |
|
Po-Hsu Lin (cypressyew) |
|
| 2018-06-12 10:32:58 |
Po-Hsu Lin |
linux-kvm (Ubuntu): assignee |
|
Po-Hsu Lin (cypressyew) |
|
| 2018-06-12 10:33:01 |
Po-Hsu Lin |
ubuntu-kernel-tests: status |
New |
In Progress |
|
| 2018-06-12 10:33:02 |
Po-Hsu Lin |
linux-kvm (Ubuntu): status |
New |
In Progress |
|
| 2018-06-12 10:36:16 |
Po-Hsu Lin |
description |
Test test_190_config_kernel_fortify from the kernel security test suite failed with 4.15.0-1008 KVM kernel.
======================================================================
FAIL: test_190_config_kernel_fortify (__main__.KernelSecurityTest)
Ensure CONFIG_FORTIFY_SOURCE is set
----------------------------------------------------------------------
Traceback (most recent call last):
File "./test-kernel-security.py", line 2186, in test_190_config_kernel_fortify
self.assertTrue(self._test_config(config_name))
AssertionError: False is not true
The CONFIG_FORTIFY_SOURCE is not set.
$ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_FORTIFY_SOURCE
# CONFIG_FORTIFY_SOURCE is not set
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8
ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17
Uname: Linux 4.15.0-1008-kvm x86_64
NonfreeKernelModules: signpost
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed Apr 25 04:28:13 2018
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install) |
== Justification ==
In the Bionic KVM kernel, the CONFIG_FORTIFY_SOURCE and
CONFIG_SECURITY_PERF_EVENTS_RESTRICT were not set, they need to be enabled to
meet the security team's requirement.
== Test ==
Before enabling the config, test case test_190_config_kernel_fortify and
test_250_config_security_perf_events_restrict will fail in the kernel
security testsuite for the kernel SRU regression test.
It will pass with these two patches applied, tested on a KVM node.
== Fix ==
Set CONFIG_SECURITY_PERF_EVENTS_RESTRICT to "y".
Set CONFIG_FORTIFY_SOURCE to "y".
== Regression Potential ==
Minimal.
No code changes, just two config change without disabling any other configs.
Test test_190_config_kernel_fortify from the kernel security test suite failed with 4.15.0-1008 KVM kernel.
======================================================================
FAIL: test_190_config_kernel_fortify (__main__.KernelSecurityTest)
Ensure CONFIG_FORTIFY_SOURCE is set
----------------------------------------------------------------------
Traceback (most recent call last):
File "./test-kernel-security.py", line 2186, in test_190_config_kernel_fortify
self.assertTrue(self._test_config(config_name))
AssertionError: False is not true
The CONFIG_FORTIFY_SOURCE is not set.
$ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_FORTIFY_SOURCE
# CONFIG_FORTIFY_SOURCE is not set
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8
ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17
Uname: Linux 4.15.0-1008-kvm x86_64
NonfreeKernelModules: signpost
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed Apr 25 04:28:13 2018
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2018-06-12 10:37:03 |
Po-Hsu Lin |
description |
== Justification ==
In the Bionic KVM kernel, the CONFIG_FORTIFY_SOURCE and
CONFIG_SECURITY_PERF_EVENTS_RESTRICT were not set, they need to be enabled to
meet the security team's requirement.
== Test ==
Before enabling the config, test case test_190_config_kernel_fortify and
test_250_config_security_perf_events_restrict will fail in the kernel
security testsuite for the kernel SRU regression test.
It will pass with these two patches applied, tested on a KVM node.
== Fix ==
Set CONFIG_SECURITY_PERF_EVENTS_RESTRICT to "y".
Set CONFIG_FORTIFY_SOURCE to "y".
== Regression Potential ==
Minimal.
No code changes, just two config change without disabling any other configs.
Test test_190_config_kernel_fortify from the kernel security test suite failed with 4.15.0-1008 KVM kernel.
======================================================================
FAIL: test_190_config_kernel_fortify (__main__.KernelSecurityTest)
Ensure CONFIG_FORTIFY_SOURCE is set
----------------------------------------------------------------------
Traceback (most recent call last):
File "./test-kernel-security.py", line 2186, in test_190_config_kernel_fortify
self.assertTrue(self._test_config(config_name))
AssertionError: False is not true
The CONFIG_FORTIFY_SOURCE is not set.
$ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_FORTIFY_SOURCE
# CONFIG_FORTIFY_SOURCE is not set
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8
ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17
Uname: Linux 4.15.0-1008-kvm x86_64
NonfreeKernelModules: signpost
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed Apr 25 04:28:13 2018
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install) |
== Justification ==
In the Bionic KVM kernel, the CONFIG_FORTIFY_SOURCE and
CONFIG_SECURITY_PERF_EVENTS_RESTRICT were not set, they need to be enabled to
meet the security team's requirement.
== Test ==
Before enabling the config, test case test_190_config_kernel_fortify and
test_250_config_security_perf_events_restrict will fail in the kernel
security testsuite for the kernel SRU regression test.
It will pass with these two patches applied, tested on a KVM node.
== Fix ==
Set CONFIG_SECURITY_PERF_EVENTS_RESTRICT to "y".
Set CONFIG_FORTIFY_SOURCE to "y".
== Regression Potential ==
Minimal.
No code changes, just two config change without disabling any other configs.
--------------------------------------------------
Test test_190_config_kernel_fortify from the kernel security test suite failed with 4.15.0-1008 KVM kernel.
======================================================================
FAIL: test_190_config_kernel_fortify (__main__.KernelSecurityTest)
Ensure CONFIG_FORTIFY_SOURCE is set
----------------------------------------------------------------------
Traceback (most recent call last):
File "./test-kernel-security.py", line 2186, in test_190_config_kernel_fortify
self.assertTrue(self._test_config(config_name))
AssertionError: False is not true
The CONFIG_FORTIFY_SOURCE is not set.
$ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_FORTIFY_SOURCE
# CONFIG_FORTIFY_SOURCE is not set
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8
ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17
Uname: Linux 4.15.0-1008-kvm x86_64
NonfreeKernelModules: signpost
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed Apr 25 04:28:13 2018
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2018-06-12 10:37:30 |
Po-Hsu Lin |
description |
== Justification ==
In the Bionic KVM kernel, the CONFIG_FORTIFY_SOURCE and
CONFIG_SECURITY_PERF_EVENTS_RESTRICT were not set, they need to be enabled to
meet the security team's requirement.
== Test ==
Before enabling the config, test case test_190_config_kernel_fortify and
test_250_config_security_perf_events_restrict will fail in the kernel
security testsuite for the kernel SRU regression test.
It will pass with these two patches applied, tested on a KVM node.
== Fix ==
Set CONFIG_SECURITY_PERF_EVENTS_RESTRICT to "y".
Set CONFIG_FORTIFY_SOURCE to "y".
== Regression Potential ==
Minimal.
No code changes, just two config change without disabling any other configs.
--------------------------------------------------
Test test_190_config_kernel_fortify from the kernel security test suite failed with 4.15.0-1008 KVM kernel.
======================================================================
FAIL: test_190_config_kernel_fortify (__main__.KernelSecurityTest)
Ensure CONFIG_FORTIFY_SOURCE is set
----------------------------------------------------------------------
Traceback (most recent call last):
File "./test-kernel-security.py", line 2186, in test_190_config_kernel_fortify
self.assertTrue(self._test_config(config_name))
AssertionError: False is not true
The CONFIG_FORTIFY_SOURCE is not set.
$ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_FORTIFY_SOURCE
# CONFIG_FORTIFY_SOURCE is not set
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8
ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17
Uname: Linux 4.15.0-1008-kvm x86_64
NonfreeKernelModules: signpost
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed Apr 25 04:28:13 2018
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install) |
== Justification ==
In the Bionic KVM kernel, the CONFIG_FORTIFY_SOURCE and
CONFIG_SECURITY_PERF_EVENTS_RESTRICT were not set, they need to be enabled to
meet the security team's requirement.
== Test ==
Before enabling the config, test case test_190_config_kernel_fortify and
test_250_config_security_perf_events_restrict will fail in the kernel
security testsuite for the kernel SRU regression test.
It will pass with these two patches applied, tested on a KVM node.
== Fix ==
Set CONFIG_SECURITY_PERF_EVENTS_RESTRICT to "y".
Set CONFIG_FORTIFY_SOURCE to "y".
== Regression Potential ==
Minimal.
No code changes, just two config change without disabling any other configs.
BugLink: https://bugs.launchpad.net/bugs/1766780
BugLink: https://bugs.launchpad.net/bugs/1766774
--------------------------------------------------
Test test_190_config_kernel_fortify from the kernel security test suite failed with 4.15.0-1008 KVM kernel.
======================================================================
FAIL: test_190_config_kernel_fortify (__main__.KernelSecurityTest)
Ensure CONFIG_FORTIFY_SOURCE is set
----------------------------------------------------------------------
Traceback (most recent call last):
File "./test-kernel-security.py", line 2186, in test_190_config_kernel_fortify
self.assertTrue(self._test_config(config_name))
AssertionError: False is not true
The CONFIG_FORTIFY_SOURCE is not set.
$ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_FORTIFY_SOURCE
# CONFIG_FORTIFY_SOURCE is not set
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8
ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17
Uname: Linux 4.15.0-1008-kvm x86_64
NonfreeKernelModules: signpost
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed Apr 25 04:28:13 2018
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2018-06-12 10:51:16 |
Po-Hsu Lin |
description |
== Justification ==
In the Bionic KVM kernel, the CONFIG_FORTIFY_SOURCE and
CONFIG_SECURITY_PERF_EVENTS_RESTRICT were not set, they need to be enabled to
meet the security team's requirement.
== Test ==
Before enabling the config, test case test_190_config_kernel_fortify and
test_250_config_security_perf_events_restrict will fail in the kernel
security testsuite for the kernel SRU regression test.
It will pass with these two patches applied, tested on a KVM node.
== Fix ==
Set CONFIG_SECURITY_PERF_EVENTS_RESTRICT to "y".
Set CONFIG_FORTIFY_SOURCE to "y".
== Regression Potential ==
Minimal.
No code changes, just two config change without disabling any other configs.
BugLink: https://bugs.launchpad.net/bugs/1766780
BugLink: https://bugs.launchpad.net/bugs/1766774
--------------------------------------------------
Test test_190_config_kernel_fortify from the kernel security test suite failed with 4.15.0-1008 KVM kernel.
======================================================================
FAIL: test_190_config_kernel_fortify (__main__.KernelSecurityTest)
Ensure CONFIG_FORTIFY_SOURCE is set
----------------------------------------------------------------------
Traceback (most recent call last):
File "./test-kernel-security.py", line 2186, in test_190_config_kernel_fortify
self.assertTrue(self._test_config(config_name))
AssertionError: False is not true
The CONFIG_FORTIFY_SOURCE is not set.
$ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_FORTIFY_SOURCE
# CONFIG_FORTIFY_SOURCE is not set
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8
ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17
Uname: Linux 4.15.0-1008-kvm x86_64
NonfreeKernelModules: signpost
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed Apr 25 04:28:13 2018
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install) |
== Justification ==
In the Bionic KVM kernel, the CONFIG_FORTIFY_SOURCE and
CONFIG_SECURITY_PERF_EVENTS_RESTRICT were not set, they need to be enabled to
meet the security team's requirement.
== Test ==
Before enabling the config, test case test_190_config_kernel_fortify and
test_250_config_security_perf_events_restrict will fail in the kernel
security testsuite for the kernel SRU regression test.
It will pass with these two patches applied, tested on a KVM node.
== Fix ==
Set CONFIG_SECURITY_PERF_EVENTS_RESTRICT to "y".
Set CONFIG_FORTIFY_SOURCE to "y".
== Regression Potential ==
Minimal.
No code changes, just two config changes without disabling any other configs.
BugLink: https://bugs.launchpad.net/bugs/1766780
BugLink: https://bugs.launchpad.net/bugs/1766774
--------------------------------------------------
Test test_190_config_kernel_fortify from the kernel security test suite failed with 4.15.0-1008 KVM kernel.
======================================================================
FAIL: test_190_config_kernel_fortify (__main__.KernelSecurityTest)
Ensure CONFIG_FORTIFY_SOURCE is set
----------------------------------------------------------------------
Traceback (most recent call last):
File "./test-kernel-security.py", line 2186, in test_190_config_kernel_fortify
self.assertTrue(self._test_config(config_name))
AssertionError: False is not true
The CONFIG_FORTIFY_SOURCE is not set.
$ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_FORTIFY_SOURCE
# CONFIG_FORTIFY_SOURCE is not set
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8
ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17
Uname: Linux 4.15.0-1008-kvm x86_64
NonfreeKernelModules: signpost
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed Apr 25 04:28:13 2018
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2018-06-22 03:04:23 |
Khaled El Mously |
linux-kvm (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2018-06-22 04:56:08 |
Po-Hsu Lin |
ubuntu-kernel-tests: status |
In Progress |
Fix Committed |
|
| 2018-06-22 08:00:58 |
Kleber Sacilotto de Souza |
bug task added |
|
linux-kvm (Ubuntu Bionic) |
|
| 2018-07-02 10:07:06 |
Kleber Sacilotto de Souza |
linux-kvm (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2018-07-20 15:44:31 |
Launchpad Janitor |
linux-kvm (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2018-08-01 08:05:37 |
Po-Hsu Lin |
ubuntu-kernel-tests: status |
Fix Committed |
Fix Released |
|
| 2018-08-01 08:05:44 |
Po-Hsu Lin |
linux-kvm (Ubuntu): status |
Fix Committed |
Fix Released |
|
