This bug was fixed in the package linux - 3.2.0-150.197
---
linux (3.2.0-150.197) precise; urgency=medium
* precise/linux: 3.2.0-150.197 -proposed tracker (LP: #1919172)
* CVE-2021-27365
- scsi: iscsi: Verify lengths on passthrough PDUs
- sysfs: Add sysfs_emit and
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not effective in some CPU and RAM combinations
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu Precise)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not effective in some CPU and RAM combinations
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Precise)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package linux - 4.15.0-36.39
---
linux (4.15.0-36.39) bionic; urgency=medium
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely
linux (4.15.0-35.38)
This bug was fixed in the package linux - 4.4.0-137.163
---
linux (4.4.0-137.163) xenial; urgency=medium
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely
linux (4.4.0-136.162)
This bug was fixed in the package linux - 3.13.0-160.210
---
linux (3.13.0-160.210) trusty; urgency=medium
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-14634
- exec: Limit arg stack to at most 75% of _STK_LIM
linux
On 2018-09-20 15:38:55, alex wrote:
> Do you have any ETA for Xenial fixed release ?
The kernels containing this fix are scheduled to be published during the
week of October 1st. If you need the fix more quickly, it is possible to
use the kernel from xenial-proposed as mentioned in comment 11.
Do you have any ETA for Xenial fixed release ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not effective in some CPU and RAM combinations
To manage notifications
I just tried on Bionic with proposed kernel. It is working too!
:~# uname -r
4.15.0-35-generic
:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename: bionic
:~# cat
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-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
I've changed the tag from verification-needed-trusty to verified-done-
trusty based on comment 15. Thanks for the testing!
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
proposed kernel for trusty still resolves this like test-kernel from #7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not effective in some CPU and RAM combinations
I don't have a trusty install to test, but #10 confirms that the test
kernel from #7 resolved it for trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not
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-
trusty' to 'verification-done-trusty'. If the problem still exists,
change the tag
It is solved with proposed kernel on Xenial, tag updated
:~# uname -a
Linux pf42.mutu.online.net 4.4.0-136-generic #162-Ubuntu SMP Tue Sep 11
15:12:40 UTC 2018
:~# cat /sys/devices/system/cpu/vulnerabilities/l1tf
Mitigation: PTE Inversion
** Tags removed: verification-needed-xenial
** Tags
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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Xenial)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
kernel from #7 resolves this on trusty as well (according to sysfs)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not effective in some CPU and RAM combinations
To
** Changed in: linux (Ubuntu Trusty)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not effective in some CPU and RAM
** Description changed:
== SRU Justification ==
- This regression has been reported in multiple bugs and affects Trust,
+ This bug has been reported in multiple bugs and affects Trusty,
Xenial and Bionic. All releases need different backports, so T and X
will be sent in separate SRU
** Changed in: linux (Ubuntu Cosmic)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not effective in some CPU and RAM
** Summary changed:
- L1TF mitigation not effective
+ L1TF mitigation not effective in some CPU and RAM combinations
** Description changed:
== SRU Justification ==
This regression has been reported in multiple bugs and affects Trust,
Xenial and Bionic. All releases need different
Bionic SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-September/095319.html
** Description changed:
+ == SRU Justification ==
+ This regression has been reported in multiple bugs and affects Trust,
+ Xenial and Bionic. All releases need different backports, so T and X
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, the bionic test kernel resolves this issue. Verified by looking at
dmesg as well as https://github.com/speed47/spectre-meltdown-checker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788563
I built Xenial and Trusty test kernels with those commits backported:
https://people.canonical.com/~tyhicks/lp1788563/xenial/
https://people.canonical.com/~tyhicks/lp1788563/trusty/
Please test the kernels and see if it resolves the bug for you. See the
comment above for details on installing
I built a Bionic test kernel with commits 9df9516, b0a182f8 and cc51e542. The
test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788563/bionic
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to
Same problem here on my Xenial system with intel-microcode
3.20180807a.0ubuntu0.16.04.1 and linux-image-4.4.0-134-generic 4.4.0-134.160,
with an Intel(R) Xeon(R) CPU E3-1220 V2 @ 3.10GHz.
L1TF: System has more than MAX_PA/2 memory. L1TF mitigation not effective.
--
You received this bug
Also, there was an off-by-one error in the calculation, that was
addressed upstream in
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b0a182f875689647b014bc01d36b340217792852
.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It's possible this issue may have been addressed by upstream commit
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cc51e5428ea54f575d49cfcede1d4cb3a72b4ec4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788563
Title:
L1TF mitigation not effective
To manage notifications about this
32 matches
Mail list logo
