16:10:41 DEBUG| [stdout] startup='Sun Aug 29 15:53:35 2021'
16:10:41 DEBUG| [stdout] tst_test.c:1346: TINFO: Timeout per run is 0h 05m 00s
16:10:41 DEBUG| [stdout] set_mempolicy05.c:66: TINFO: stack pattern is in 0xbf996ccc-0xbf9970cc
16:10:41 DEBUG| [stdout] set_mempolicy05.c:111: TFAIL: set_mempolicy should fail with EFAULT or EINVAL, instead returned 38
16:10:41 DEBUG| [stdout]
16:10:41 DEBUG| [stdout] HINT: You _MAY_ be missing kernel fixes, see:
16:10:41 DEBUG| [stdout]
16:10:41 DEBUG| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cf01fb9985e8
16:10:41 DEBUG| [stdout]
16:10:41 DEBUG| [stdout] HINT: You _MAY_ be vulnerable to CVE(s), see:
16:10:41 DEBUG| [stdout]
16:10:41 DEBUG| [stdout] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-CVE-2017-7616
16:10:41 DEBUG| [stdout]
16:10:41 DEBUG| [stdout] Summary:
16:10:41 DEBUG| [stdout] passed 0
16:10:41 DEBUG| [stdout] failed 1
16:10:41 DEBUG| [stdout] broken 0
16:10:41 DEBUG| [stdout] skipped 0
16:10:41 DEBUG| [stdout] warnings 0
16:10:41 DEBUG| [stdout] tag=cve-2017-7616 stime=1630252415 dur=0 exit=exited stat=1 core=no cu=0 cs=0
This is not a regression as this is a new testcase which runs only on 32-bit systems (i386 and powerpc).
The commit sha1 (cf01fb9985e8deb25ccf0ea54d916b8871ae0e62 - mm/mempolicy.c: fix error handling in set_mempolicy and mbind.) which fixes this CVE, according to https://ubuntu.com/security/CVE-2017-7616, was applied upstream for v4.11-rc6, so both focal/linux and bionic/linux supposedly contain the fix.
ubuntu_ltp.cve cve-2017-7616 testcase output:
16:10:41 DEBUG| [stdout] startup='Sun Aug 29 15:53:35 2021' .c:66: TINFO: stack pattern is in 0xbf996ccc- 0xbf9970cc .c:111: TFAIL: set_mempolicy should fail with EFAULT or EINVAL, instead returned 38 /git.kernel. org/pub/ scm/linux/ kernel/ git/torvalds/ linux.git/ commit/ ?id=cf01fb9985e 8 /cve.mitre. org/cgi- bin/cvename. cgi?name= CVE-CVE- 2017-7616
16:10:41 DEBUG| [stdout] tst_test.c:1346: TINFO: Timeout per run is 0h 05m 00s
16:10:41 DEBUG| [stdout] set_mempolicy05
16:10:41 DEBUG| [stdout] set_mempolicy05
16:10:41 DEBUG| [stdout]
16:10:41 DEBUG| [stdout] HINT: You _MAY_ be missing kernel fixes, see:
16:10:41 DEBUG| [stdout]
16:10:41 DEBUG| [stdout] https:/
16:10:41 DEBUG| [stdout]
16:10:41 DEBUG| [stdout] HINT: You _MAY_ be vulnerable to CVE(s), see:
16:10:41 DEBUG| [stdout]
16:10:41 DEBUG| [stdout] https:/
16:10:41 DEBUG| [stdout]
16:10:41 DEBUG| [stdout] Summary:
16:10:41 DEBUG| [stdout] passed 0
16:10:41 DEBUG| [stdout] failed 1
16:10:41 DEBUG| [stdout] broken 0
16:10:41 DEBUG| [stdout] skipped 0
16:10:41 DEBUG| [stdout] warnings 0
16:10:41 DEBUG| [stdout] tag=cve-2017-7616 stime=1630252415 dur=0 exit=exited stat=1 core=no cu=0 cs=0
This is not a regression as this is a new testcase which runs only on 32-bit systems (i386 and powerpc).
The commit sha1 (cf01fb9985e8de b25ccf0ea54d916 b8871ae0e62 - mm/mempolicy.c: fix error handling in set_mempolicy and mbind.) which fixes this CVE, according to https:/ /ubuntu. com/security/ CVE-2017- 7616, was applied upstream for v4.11-rc6, so both focal/linux and bionic/linux supposedly contain the fix.