Date
1 - 4 of 4
[cip-kernel-sec 3/3] issues: fill in the description field of remaining CVEs
|
Daniel Sangorrin <daniel.sangorrin@...>
From: nguyen van hieu <hieu2.nguyenvan@...>
I noticed that some issues have the description field empty when using the --show-description option. Signed-off-by: nguyen van hieu <hieu2.nguyenvan@...> Signed-off-by: Daniel Sangorrin <daniel.sangorrin@...> --- issues/CVE-2016-6213.yml | 5 ++++- issues/CVE-2017-1000364.yml | 5 ++++- issues/CVE-2017-1000365.yml | 6 +++++- issues/CVE-2017-1000379.yml | 5 ++++- issues/CVE-2017-16538.yml | 5 ++++- issues/CVE-2019-15214.yml | 6 +++++- issues/CVE-2019-20794.yml | 6 +++++- issues/CVE-2020-11725.yml | 8 +++++++- 8 files changed, 38 insertions(+), 8 deletions(-) diff --git a/issues/CVE-2016-6213.yml b/issues/CVE-2016-6213.yml index 31762df..58bf472 100644 --- a/issues/CVE-2016-6213.yml +++ b/issues/CVE-2016-6213.yml @@ -1,4 +1,7 @@ -description: '' +description: |- + fs/namespace.c in the Linux kernel before 4.9 does not restrict how many mounts may exist in a mount namespace, + which allows local users to cause a denial of service (memory consumption and deadlock) via MS_BIND mount system calls, + as demonstrated by a loop that triggers exponential growth in the number of mounts. references: - http://www.openwall.com/lists/oss-security/2016/07/13/6 - https://lkml.org/lkml/2016/8/28/269 diff --git a/issues/CVE-2017-1000364.yml b/issues/CVE-2017-1000364.yml index 8841754..c566c5b 100644 --- a/issues/CVE-2017-1000364.yml +++ b/issues/CVE-2017-1000364.yml @@ -1,4 +1,7 @@ -description: '' +description: |- + An issue was discovered in the size of the stack guard page on Linux, specifically a 4k stack guard + page is not sufficiently large and can be "jumped" over (the stack guard page is bypassed), + this affects Linux Kernel versions 4.11.5 and earlier (the stackguard page was introduced in 2010). references: - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000364 - http://www.ubuntu.com/usn/usn-3324-1 diff --git a/issues/CVE-2017-1000365.yml b/issues/CVE-2017-1000365.yml index 6cbae0b..f87ca53 100644 --- a/issues/CVE-2017-1000365.yml +++ b/issues/CVE-2017-1000365.yml @@ -1,4 +1,8 @@ -description: '' +description: |- + The Linux Kernel imposes a size restriction on the arguments and environmental strings passed through + RLIMIT_STACK/RLIM_INFINITY (1/4 of the size), but does not take the argument and environment pointers + into account, which allows attackers to bypass this limitation. This affects Linux Kernel versions 4.11.5 and earlier. + It appears that this feature was introduced in the Linux Kernel version 2.6.23. references: - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000365 - https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt diff --git a/issues/CVE-2017-1000379.yml b/issues/CVE-2017-1000379.yml index 93258d8..2ae11b1 100644 --- a/issues/CVE-2017-1000379.yml +++ b/issues/CVE-2017-1000379.yml @@ -1,4 +1,7 @@ -description: '' +description: |- + The Linux Kernel running on AMD64 systems will sometimes map the contents of PIE executable, + the heap or ld.so to where the stack is mapped allowing attackers to more easily manipulate the stack. + Linux Kernel version 4.11.5 is affected. references: - https://www.qualys.com/2017/06/19/stack-clash/stack-clash.txt - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000379 diff --git a/issues/CVE-2017-16538.yml b/issues/CVE-2017-16538.yml index 793db3f..c466041 100644 --- a/issues/CVE-2017-16538.yml +++ b/issues/CVE-2017-16538.yml @@ -1,4 +1,7 @@ -description: '' +description: |- + drivers/media/usb/dvb-usb-v2/lmedm04.c in the Linux kernel through 4.13.11 allows local users to cause a denial of service + (general protection fault and system crash) or possibly have unspecified other impact via a crafted USB device, + related to a missing warm-start check and incorrect attach timing (dm04_lme2510_frontend_attach versus dm04_lme2510_tuner). references: - https://patchwork.linuxtv.org/patch/44566/ - https://patchwork.linuxtv.org/patch/44567/ diff --git a/issues/CVE-2019-15214.yml b/issues/CVE-2019-15214.yml index c92091b..cb6006d 100644 --- a/issues/CVE-2019-15214.yml +++ b/issues/CVE-2019-15214.yml @@ -1,4 +1,8 @@ -description: '' +description: |- + An issue was discovered in the Linux kernel before 5.0.10. + There is a use-after-free in the sound subsystem because + card disconnection causes certain data structures to be deleted too early. + This is related to sound/core/init.c and sound/core/info.c. references: - https://syzkaller.appspot.com/bug?id=75903e0021cef79bc434d068b5169b599b2a46a9 - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15214 diff --git a/issues/CVE-2019-20794.yml b/issues/CVE-2019-20794.yml index 43e3ccf..8f30e12 100644 --- a/issues/CVE-2019-20794.yml +++ b/issues/CVE-2019-20794.yml @@ -1,4 +1,8 @@ -description: '' +description: |- + An issue was discovered in the Linux kernel 4.18 through 5.6.11 when unprivileged user namespaces are allowed. + A user can create their own PID namespace, and mount a FUSE filesystem. Upon interaction with this FUSE filesystem, + if the userspace component is terminated via a kill of the PID namespace's pid 1, it will result in a hung task, + and resources being permanently locked up until system reboot. This can result in resource exhaustion. references: - https://github.com/sargun/fuse-example - https://sourceforge.net/p/fuse/mailman/message/36598753/ diff --git a/issues/CVE-2020-11725.yml b/issues/CVE-2020-11725.yml index ca2b80d..3cae05d 100644 --- a/issues/CVE-2020-11725.yml +++ b/issues/CVE-2020-11725.yml @@ -1,4 +1,10 @@ -description: '' +description: |- + ** DISPUTED ** snd_ctl_elem_add in sound/core/control.c in the Linux kernel through 5.6.3 has a count=info->owner line, + which later affects a private_size*count multiplication for unspecified "interesting side effects." + NOTE: kernel engineers dispute this finding, because it could be relevant only if new callers were added + that were unfamiliar with the misuse of the info->owner field to represent data unrelated to the "owner" concept. + The existing callers, SNDRV_CTL_IOCTL_ELEM_ADD and SNDRV_CTL_IOCTL_ELEM_REPLACE, + have been designed to misuse the info->owner field in a safe way. references: - https://twitter.com/yabbadabbadrew/status/1248632267028582400 - https://lore.kernel.org/alsa-devel/s5h4ktmlfpx.wl-tiwai@suse.de/ -- 2.25.1 |
|
|
|
Chen-Yu Tsai (Moxa) <wens@...>
On Fri, Sep 25, 2020 at 12:01 PM Daniel Sangorrin
<daniel.sangorrin@...> wrote: Looks like all the new descriptions were copied from MITRE. Reviewed-by: Chen-Yu Tsai (Moxa) <wens@...> |
|
|
|
Daniel Sangorrin <daniel.sangorrin@...>
Hello Chen-yu,
toggle quoted message
Show quoted text
Thanks for your check. -----Original Message-----Is there a problem with that? The MITRE license is included in the COPYING file as far as I know. Thanks, Daniel |
|
|
|
Chen-Yu Tsai (Moxa) <wens@...>
On Wed, Oct 14, 2020 at 12:16 PM Daniel Sangorrin
<daniel.sangorrin@...> wrote: Not at all. I'm merely stating that the descriptions match a known source. ChenYu |
|
|