Passed with F-intel-5.13.0-1007.7
** Changed in: linux-signed-oem-5.13 (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: linux-intel-5.13 (Ubuntu Focal)
Status: Confirmed => Fix Released
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
--
Found this on Intel 5.13 5.13.0-1004.4
** Also affects: linux-intel-5.13 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-intel-5.13 (Ubuntu)
Status: New => Invalid
** Changed in: linux-intel-5.13 (Ubuntu Focal)
Status: New => Confirmed
--
You received
Test passed with 5.13.0-1012.16
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3609
** Changed in: linux-signed-oem-5.13 (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: linux-signed-oem-5.13 (Ubuntu)
Status: New => Invalid
--
You received this bug
I can reproduce this issue on 5.13.0-1010 by running this test case.
To run this test you will need to build LTP for it.
sudo apt install -y automake bison build-essential byacc flex git keyutils
libacl1-dev libaio-dev libcap-dev libmm-dev libnuma-dev libsctp-dev
libselinux1-dev libssl-dev
** Description changed:
It looks like this is a test case for CVE-2021-3609
+
+ This issue does not exist in the last cycle for OEM 5.13.0-1010 as this
+ test case does not exist back then.
can_bcm01 test in ubuntu_ltp_stable/can will trigger the following error on
5.13.0-1011-oem and
