← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1899993] Re: EFI: Fails when BootCurrent entry does not exist

 

This bug was fixed in the package linux - 5.8.0-36.40+21.04.1

---------------
linux (5.8.0-36.40+21.04.1) hirsute; urgency=medium

  * Packaging resync (LP: #1786013)
    - update dkms package versions

  [ Ubuntu: 5.8.0-36.40 ]

  * debian/scripts/file-downloader does not handle positive failures correctly
    (LP: #1878897)
    - [Packaging] file-downloader not handling positive failures correctly

  [ Ubuntu: 5.8.0-35.39 ]

  * Packaging resync (LP: #1786013)
    - update dkms package versions
  * CVE-2021-1052 // CVE-2021-1053
    - [Packaging] NVIDIA -- Add the NVIDIA 460 driver

 -- Kleber Sacilotto de Souza <kleber.souza@xxxxxxxxxxxxx>  Thu, 07 Jan
2021 11:57:30 +0100

** Changed in: linux (Ubuntu Hirsute)
       Status: Fix Committed => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1052

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-1053

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1899993

Title:
  EFI: Fails when BootCurrent entry does not exist

Status in curtin package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in curtin source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in curtin source package in Focal:
  Invalid
Status in linux source package in Focal:
  Fix Released
Status in curtin source package in Groovy:
  Invalid
Status in linux source package in Groovy:
  Fix Released
Status in curtin source package in Hirsute:
  Invalid
Status in linux source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  MAAS installs fail on systems that have EFI Variables that include a "/" in the name.

  Split out of bug 1894217.

  [Test Case]
  Using an OVMF-based VM, create a boot variable with a "/" character. For example:

  Shell> setvar FOO/BAR -guid 8ed72b3f-ad26-4d5c-aa36-38689635cac3 -rt
  -nv =foo

  Then, in Linux:

  $ ls /sys/firmware/efi/efivars/
  ls: reading directory '/sys/firmware/efi/efivars/': Input/output error
  BootOrder-8be4df61-93ca-11d2-aa0d-00e098032b8c
  ConIn-8be4df61-93ca-11d2-aa0d-00e098032b8c
  ConOut-8be4df61-93ca-11d2-aa0d-00e098032b8c
  ErrOut-8be4df61-93ca-11d2-aa0d-00e098032b8c
  MTC-eb704011-1402-11d3-8e77-00a0c969723b

  The Input/output error is the key symptom. See below to see how that
  percolates up to MAAS install failures.

  [Regression Risk]
  There's a very tiny chance that someone has written code that depends on an the -EIO error for some reason. It's hard to guess why such a script would do that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1899993/+subscriptions