Comment 2 for bug 1927794
Revision history for this message
| Thadeu Lima de Souza Cascardo (cascardo) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
You should see this failure on all 4.15 kernels. CVE-2021-3444 was due to differences in behavior on division by 0 but also on the 32-bit ALU32 bounds tracking. Our 4.15 kernels do not carry the ALU32 bounds tracking support, so are not vulnerable to the attack. We decided to keep the difference in behavior to avoid regressions.
We might decide to add the said commit and test it with this particular LTP test, if we decide there is more value than simply silencing a test failure. Given the reason that behavior change was introduced, I think it's worth it. We just need to take care not to introduce CVE-2021-3444 or other vulnerability when we do it.
Cascardo.