VYPR

rpm package

suse/kernel-syms&distro=SUSE Linux Enterprise Server 12 SP4

pkg:rpm/suse/kernel-syms&distro=SUSE%20Linux%20Enterprise%20Server%2012%20SP4

Vulnerabilities (224)

  • CVE-2019-18683Nov 4, 2019
    affected < 4.12.14-95.45.1fixed 4.12.14-95.45.1

    An issue was discovered in drivers/media/platform/vivid in the Linux kernel through 5.3.8. It is exploitable for privilege escalation on some Linux distributions where local users have /dev/video0 access, but only if the driver happens to be loaded. There are multiple race condit

  • CVE-2019-17666Oct 17, 2019
    affected < 4.12.14-95.37.1fixed 4.12.14-95.37.1

    rtl_p2p_noa_ie in drivers/net/wireless/realtek/rtlwifi/ps.c in the Linux kernel through 5.3.6 lacks a certain upper-bound check, leading to a buffer overflow.

  • CVE-2019-17133Oct 4, 2019
    affected < 4.12.14-95.37.1fixed 4.12.14-95.37.1

    In the Linux kernel through 5.3.2, cfg80211_mgd_wext_giwessid in net/wireless/wext-sme.c does not reject a long SSID IE, leading to a Buffer Overflow.

  • CVE-2019-17055Oct 1, 2019
    affected < 4.12.14-95.45.1fixed 4.12.14-95.45.1

    base_sock_create in drivers/isdn/mISDN/socket.c in the AF_ISDN network module in the Linux kernel through 5.3.2 does not enforce CAP_NET_RAW, which means that unprivileged users can create a raw socket, aka CID-b91ee4aa2a21.

  • CVE-2019-17056Oct 1, 2019
    affected < 4.12.14-95.37.1fixed 4.12.14-95.37.1

    llcp_sock_create in net/nfc/llcp_sock.c in the AF_NFC network module in the Linux kernel through 5.3.2 does not enforce CAP_NET_RAW, which means that unprivileged users can create a raw socket, aka CID-3a359798b176.

  • CVE-2019-16994Sep 30, 2019
    affected < 4.12.14-95.48.1fixed 4.12.14-95.48.1

    In the Linux kernel before 5.0, a memory leak exists in sit_init_net() in net/ipv6/sit.c when register_netdev() fails to register sitn->fb_tunnel_dev, which may cause denial of service, aka CID-07f12b26e21a.

  • CVE-2019-14814Sep 20, 2019
    affected < 4.12.14-95.32.1fixed 4.12.14-95.32.1

    There is heap-based buffer overflow in Linux kernel, all versions up to, excluding 5.3, in the marvell wifi chip driver in Linux kernel, that allows local users to cause a denial of service(system crash) or possibly execute arbitrary code.

  • CVE-2019-14816Sep 20, 2019
    affected < 4.12.14-95.32.1fixed 4.12.14-95.32.1

    There is heap-based buffer overflow in kernel, all versions up to, excluding 5.3, in the marvell wifi chip driver in Linux kernel, that allows local users to cause a denial of service(system crash) or possibly execute arbitrary code.

  • CVE-2019-14821Sep 19, 2019
    affected < 4.12.14-95.37.1fixed 4.12.14-95.37.1

    An out-of-bounds access issue was found in the Linux kernel, all versions through 5.3, in the way Linux kernel's KVM hypervisor implements the Coalesced MMIO write operation. It operates on an MMIO ring buffer 'struct kvm_coalesced_mmio' object, wherein write indices 'ring->first

  • CVE-2019-14835Sep 17, 2019
    affected < 4.12.14-95.32.1fixed 4.12.14-95.32.1

    A buffer overflow flaw was found, in versions from 2.6.34 to 5.2.x, in the way Linux kernel's vhost functionality that translates virtqueue buffers to IOVs, logged the buffer descriptors during migration. A privileged guest user able to pass descriptors with invalid length to the

  • CVE-2019-15031Sep 13, 2019
    affected < 4.12.14-95.32.1fixed 4.12.14-95.32.1

    In the Linux kernel through 5.2.14 on the powerpc platform, a local user can read vector registers of other users' processes via an interrupt. To exploit the venerability, a local user starts a transaction (via the hardware transactional memory instruction tbegin) and then access

  • CVE-2019-15030Sep 13, 2019
    affected < 4.12.14-95.32.1fixed 4.12.14-95.32.1

    In the Linux kernel through 5.2.14 on the powerpc platform, a local user can read vector registers of other users' processes via a Facility Unavailable exception. To exploit the venerability, a local user starts a transaction (via the hardware transactional memory instruction tbe

  • CVE-2019-16231Sep 11, 2019
    affected < 4.12.14-95.45.1fixed 4.12.14-95.45.1

    drivers/net/fjes/fjes_main.c in the Linux kernel 5.2.14 does not check the alloc_workqueue return value, leading to a NULL pointer dereference.

  • CVE-2019-16232Sep 11, 2019
    affected < 4.12.14-95.37.1fixed 4.12.14-95.37.1

    drivers/net/wireless/marvell/libertas/if_sdio.c in the Linux kernel 5.2.14 does not check the alloc_workqueue return value, leading to a NULL pointer dereference.

  • CVE-2019-16233Sep 11, 2019
    affected < 4.12.14-95.40.1fixed 4.12.14-95.40.1

    drivers/scsi/qla2xxx/qla_os.c in the Linux kernel 5.2.14 does not check the alloc_workqueue return value, leading to a NULL pointer dereference.

  • CVE-2019-16234Sep 11, 2019
    affected < 4.12.14-95.37.1fixed 4.12.14-95.37.1

    drivers/net/wireless/intel/iwlwifi/pcie/trans.c in the Linux kernel 5.2.14 does not check the alloc_workqueue return value, leading to a NULL pointer dereference.

  • CVE-2019-9455Sep 6, 2019
    affected < 4.12.14-95.54.1fixed 4.12.14-95.54.1

    In the Android kernel in the video driver there is a kernel pointer leak due to a WARN_ON statement. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.

  • CVE-2019-9458Sep 6, 2019
    affected < 4.12.14-95.51.1fixed 4.12.14-95.51.1

    In the Android kernel in the video driver there is a use after free due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

  • CVE-2019-9456Sep 6, 2019
    affected < 4.12.14-95.32.1fixed 4.12.14-95.32.1

    In the Android kernel in Pixel C USB monitor driver there is a possible OOB write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

  • CVE-2017-18595Sep 4, 2019
    affected < 4.12.14-95.37.1fixed 4.12.14-95.37.1

    An issue was discovered in the Linux kernel before 4.14.11. A double free may be caused by the function allocate_trace_buffer in the file kernel/trace/trace.c.

Page 6 of 12