Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #949696
| From | Christoph Müllner <christoph.muellner@theobroma-systems.com> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#923988: /boot/vmlinuz-4.19.0-2-arm64: dmidecode causes kernel panic (puma-rk3399) |
| Date | 2019-03-12 22:10 +0100 |
| Message-ID | <xAWOR-2xr-11@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <xzbIl-tw-1@gated-at.bofh.it> <xAUk1-PH-1@gated-at.bofh.it> <xAWOR-2xr-1@gated-at.bofh.it> <xzbIl-tw-1@gated-at.bofh.it> <xAWOR-2xr-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
On 3/12/19 9:57 PM, Ben Hutchings wrote: > On Tue, 2019-03-12 at 19:04 +0100, Christoph Müllner wrote: >> I've been able to reproduce and analyse this issue. >> >> The security error seems to be valid. > [...] > > I don't see a security issue here. The kernel does not and should not > stop root breaking the system with direct access to /dev/mem, *unless* > Secure Boot / lockdown is active - and in that case access to /dev/mem > is blocked completely. You are right. There is no security error. SError stands for system error.
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Find similar | Unroll thread
Bug#923988: /boot/vmlinuz-4.19.0-2-arm64: dmidecode causes kernel panic (puma-rk3399) Vagrant Cascadian <vagrant@debian.org> - 2019-03-08 01:40 +0100
Bug#923988: /boot/vmlinuz-4.19.0-2-arm64: dmidecode causes kernel panic (puma-rk3399) Christoph Müllner <christoph.muellner@theobroma-systems.com> - 2019-03-12 19:30 +0100
Bug#923988: /boot/vmlinuz-4.19.0-2-arm64: dmidecode causes kernel panic (puma-rk3399) Ben Hutchings <ben@decadent.org.uk> - 2019-03-12 22:10 +0100
Bug#923988: /boot/vmlinuz-4.19.0-2-arm64: dmidecode causes kernel panic (puma-rk3399) Christoph Müllner <christoph.muellner@theobroma-systems.com> - 2019-03-12 22:10 +0100
csiph-web