Bug 2181840 - F38 Secure Boot dbx Configuration Update 190 -> 217 fails w/Invalid argument
Summary: F38 Secure Boot dbx Configuration Update 190 -> 217 fails w/Invalid argument
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 38
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-26 13:47 UTC by browseria
Modified: 2023-03-28 06:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description browseria 2023-03-26 13:47:31 UTC
Description of problem:
When installing Fedora 38 into a KVM virtual image using `virt-install --boot uefi`,
it defaults to using the OVMF 2M files. Fedora 38 currently ships with dbx
Configuration Update 190, so one of the updates a user will first encounter is the
"Secure Boot dbx Configuration Update 190 -> 217". Attempting to apply this update
through Software silently fails, and through fwdupdmgr results in:

> failed to write data to efivarfs: Error writing to file descriptor: Invalid argument

What really happened is the UEFI variable store in the 2M OVMF files is too small
to be able to apply this update. Switching to using the ovmf-4m files shipped with
Fedora 38 removes this issue and the update can then be applied correctly.

What I'd like to see is the `virt-install --boot uefi` option default to using the
OVMF 4M files instead of using the current OVMF 2M files, and that Fedora 38 ship
with "Secure Boot dbx Configuration Update 217". Otherwise, the user of the VM
will have this update for the entire lifetime of F38 and never be able to apply it.
I believe the dbx update is a security update, so this adds to the concern.


Version-Release number of selected component (if applicable):
virt-install 4.1.0


How reproducible:
Every time when using `--boot uefi`.


Steps to Reproduce:
1. `virt-install --boot uefi --osinfo detect=off,name=fedora38 --arch x86_64 --machine q35 ...`
2. Go to Software and try to apply the "Secure Boot dbx Configuration Update 190 -> 217" 
3. OR `fwupdmgr update`


Actual results:
Software silently fails, and fwupdmgr reports:
> failed to write data to efivarfs: Error writing to file descriptor: Invalid argument


Expected results:
The update succeeds and the dbx is updated to 217.


Additional info:
See the discussion here for more details:

https://discussion.fedoraproject.org/t/f38-secure-boot-dbx-configuration-update-190-217-fails-w-invalid-argument/79822


Note You need to log in before you can comment on or make changes to this bug.