e1000e blocks the boot process when it tried to write checksum to its NVM
Bug #1936998 reported by
AceLan Kao
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
AceLan Kao | ||
Focal |
Fix Released
|
Undecided
|
AceLan Kao | ||
Hirsute |
Fix Released
|
Undecided
|
AceLan Kao | ||
Impish |
Fix Released
|
Undecided
|
AceLan Kao | ||
linux-oem-5.10 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
AceLan Kao | ||
Hirsute |
Invalid
|
Undecided
|
Unassigned | ||
Impish |
Invalid
|
Undecided
|
Unassigned | ||
linux-oem-5.13 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
AceLan Kao | ||
Hirsute |
Invalid
|
Undecided
|
Unassigned | ||
Impish |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
While probing e1000e, it checks its NVM checksum, and write correct checksum back if the checksum is not correct. But for recent GBE update for security, its NVM could be written once for MAC address during production, so write checksum during driver probing is not allowed and would block the boot process.
[Fix]
Intel provides a fix for it.
https:/
[Test]
Verified on a Dell machine which has wrong NVM checksum.
[Where problems could occur]
From what Intel told us, the checksum isn't correct is not a big deal, we could ignore it and it won't lead to any issues.
CVE References
tags: | added: oem-priority originate-from-1934511 somerville |
Changed in linux (Ubuntu Focal): | |
status: | New → In Progress |
Changed in linux (Ubuntu Hirsute): | |
status: | New → In Progress |
Changed in linux (Ubuntu Impish): | |
status: | New → In Progress |
Changed in linux (Ubuntu Focal): | |
assignee: | nobody → AceLan Kao (acelankao) |
Changed in linux (Ubuntu Hirsute): | |
assignee: | nobody → AceLan Kao (acelankao) |
Changed in linux (Ubuntu Impish): | |
assignee: | nobody → AceLan Kao (acelankao) |
Changed in linux-oem-5.10 (Ubuntu Focal): | |
assignee: | nobody → AceLan Kao (acelankao) |
status: | New → In Progress |
Changed in linux-oem-5.13 (Ubuntu Focal): | |
assignee: | nobody → AceLan Kao (acelankao) |
status: | New → In Progress |
Changed in linux-oem-5.10 (Ubuntu Hirsute): | |
status: | New → Invalid |
Changed in linux-oem-5.10 (Ubuntu Impish): | |
status: | New → Invalid |
Changed in linux-oem-5.13 (Ubuntu Hirsute): | |
status: | New → Invalid |
Changed in linux-oem-5.13 (Ubuntu Impish): | |
status: | New → Invalid |
Changed in linux-oem-5.10 (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
Changed in linux-oem-5.13 (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-focal removed: verification-needed-focal |
Changed in linux (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Hirsute): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-hirsute removed: verification-needed-hirsute |
Changed in hwe-next: | |
status: | New → Fix Released |
To post a comment you must log in.
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- focal' to 'verification- done-focal' . If the problem still exists, change the tag 'verification- needed- focal' to 'verification- failed- focal'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!