off-by-one bug in L1TF mitigation
Bug #1789834 reported by
Markus Schade
This bug report is a duplicate of:
Bug #1788563: L1TF mitigation not effective in some CPU and RAM combinations.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
| Trusty |
Triaged
|
Medium
|
Unassigned | ||
| Xenial |
Triaged
|
Medium
|
Unassigned | ||
| Bionic |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
due to an off-by-one bug in the L1TF patch, the "rare" case of systems still vulnerable
is more frequent.
This typically happens on Nehalem+ destop/entry-level server systems with 32G memory installed.
Originally this was reported in OpenSUSE, but I can confirm this is also happens with the latest trusty kernel (3.13.0-
The following patch increases the memory limit for the mitigation on these systems in general:
| description: | updated |
| Changed in linux (Ubuntu): | |
| status: | New → Confirmed |
| Changed in linux (Ubuntu): | |
| importance: | Undecided → Medium |
| Changed in linux (Ubuntu Trusty): | |
| status: | New → Incomplete |
| Changed in linux (Ubuntu): | |
| status: | Confirmed → Incomplete |
| Changed in linux (Ubuntu Trusty): | |
| importance: | Undecided → Medium |
| status: | Incomplete → Triaged |
| Changed in linux (Ubuntu): | |
| status: | Incomplete → Triaged |
| tags: | added: kernel-da-key trusty |
Revision history for this message
| Markus Schade (lp-markusschade) wrote | #1 |
| Changed in linux (Ubuntu Xenial): | |
| status: | New → Triaged |
| Changed in linux (Ubuntu Bionic): | |
| status: | New → Triaged |
| Changed in linux (Ubuntu Xenial): | |
| importance: | Undecided → Medium |
| Changed in linux (Ubuntu Bionic): | |
| importance: | Undecided → Medium |
| tags: | added: cscc |
To post a comment you must log in.
This happens pretty much on all Ubuntu kernels with the initial L1TF implementation, so xenial, bionic and cosmic are also affected.
https:/
https:/