ALSA-2020:4431 (CVE-2019-12614)

Vulnerability from osv_almalinux – Published: 2020-11-03 12:03 – Updated: 2021-08-11 08:54 – Source website
VLAI
Summary
Moderate: kernel security, bug fix, and enhancement update
Details

The kernel packages contain the Linux kernel, the core of any Linux operating system.

Security Fix(es):

  • kernel: use after free in the video driver leads to local privilege escalation (CVE-2019-9458)

  • kernel: use-after-free in drivers/bluetooth/hci_ldisc.c (CVE-2019-15917)

  • kernel: out-of-bounds access in function hclge_tm_schd_mode_vnet_base_cfg (CVE-2019-15925)

  • kernel: memory leak in ccp_run_sha_cmd() (CVE-2019-18808)

  • kernel: Denial Of Service in the __ipmi_bmc_register() (CVE-2019-19046)

  • kernel: out-of-bounds write in ext4_xattr_set_entry (CVE-2019-19319)

  • Kernel: kvm: OOB memory write via kvm_dev_ioctl_get_cpuid (CVE-2019-19332)

  • kernel: use-after-free in ext4_put_super (CVE-2019-19447)

  • kernel: a malicious USB device in the drivers/input/ff-memless.c leads to use-after-free (CVE-2019-19524)

  • kernel: race condition caused by a malicious USB device in the USB character device driver layer (CVE-2019-19537)

  • kernel: use-after-free in serial_ir_init_module() (CVE-2019-19543)

  • kernel: use-after-free in __ext4_expand_extra_isize and ext4_xattr_set_entry (CVE-2019-19767)

  • kernel: use-after-free in debugfs_remove (CVE-2019-19770)

  • kernel: out-of-bounds write via crafted keycode table (CVE-2019-20636)

  • kernel: possible use-after-free due to a race condition in cdev_get (CVE-2020-0305)

  • kernel: out-of-bounds read in in vc_do_resize function (CVE-2020-8647)

  • kernel: use-after-free in n_tty_receive_buf_common function (CVE-2020-8648)

  • kernel: invalid read location in vgacon_invert_region function (CVE-2020-8649)

  • kernel: uninitialized kernel data leak in userspace coredumps (CVE-2020-10732)

  • kernel: SELinux netlink permission check bypass (CVE-2020-10751)

  • kernel: out-of-bounds write in mpol_parse_str (CVE-2020-11565)

  • kernel: mishandles invalid descriptors in drivers/media/usb/gspca/xirlink_cit.c (CVE-2020-11668)

  • kernel: buffer overflow in mt76_add_fragment function (CVE-2020-12465)

  • kernel: xdp_umem_reg in net/xdp/xdp_umem.c has an out-of-bounds write which could result in crash and data coruption (CVE-2020-12659)

  • kernel: sg_write function lacks an sg_remove_request call in a certain failure case (CVE-2020-12770)

  • kernel: possible to send arbitrary signals to a privileged (suidroot) parent process (CVE-2020-12826)

  • kernel: referencing inode of removed superblock in get_futex_key() causes UAF (CVE-2020-14381)

  • kernel: soft-lockups in iov_iter_copy_from_user_atomic() could result in DoS (CVE-2020-25641)

  • kernel: kernel pointer leak due to WARN_ON statement in video driver leads to local information disclosure (CVE-2019-9455)

  • kernel: null pointer dereference in dlpar_parse_cc_property (CVE-2019-12614)

  • kernel: null-pointer dereference in drivers/net/fjes/fjes_main.c (CVE-2019-16231)

  • kernel: null pointer dereference in drivers/scsi/qla2xxx/qla_os.c (CVE-2019-16233)

  • kernel: memory leak in af9005_identify_state() function (CVE-2019-18809)

  • kernel: A memory leak in the mwifiex_pcie_alloc_cmdrsp_buf() function (CVE-2019-19056)

  • kernel: memory leak in the crypto_report() function (CVE-2019-19062)

  • kernel: Two memory leaks in the rtl_usb_probe() function (CVE-2019-19063)

  • kernel: A memory leak in the rtl8xxxu_submit_int_urb() function (CVE-2019-19068)

  • kernel: A memory leak in the predicate_parse() function (CVE-2019-19072)

  • kernel: information leak bug caused by a malicious USB device in the drivers/media/usb/ttusb-dec/ttusb_dec.c (CVE-2019-19533)

  • kernel: Null pointer dereference in drop_sysctl_table() (CVE-2019-20054)

  • kernel: kernel stack information leak on s390/s390x (CVE-2020-10773)

  • kernel: possibility of memory disclosure when reading the file /proc/sys/kernel/rh_features (CVE-2020-10774)

  • kernel: vhost-net: stack overflow in get_raw_socket while checking sk_family field (CVE-2020-10942)

  • kernel: sync of excessive duration via an XFS v5 image with crafted metadata (CVE-2020-12655)

References
https://vulners.com/cve/CVE-2019-12614 REPORT
https://vulners.com/cve/CVE-2019-15917 REPORT
https://vulners.com/cve/CVE-2019-15925 REPORT
https://vulners.com/cve/CVE-2019-16231 REPORT
https://vulners.com/cve/CVE-2019-16233 REPORT
https://vulners.com/cve/CVE-2019-18808 REPORT
https://vulners.com/cve/CVE-2019-18809 REPORT
https://vulners.com/cve/CVE-2019-19046 REPORT
https://vulners.com/cve/CVE-2019-19056 REPORT
https://vulners.com/cve/CVE-2019-19062 REPORT
https://vulners.com/cve/CVE-2019-19063 REPORT
https://vulners.com/cve/CVE-2019-19068 REPORT
https://vulners.com/cve/CVE-2019-19072 REPORT
https://vulners.com/cve/CVE-2019-19319 REPORT
https://vulners.com/cve/CVE-2019-19332 REPORT
https://vulners.com/cve/CVE-2019-19447 REPORT
https://vulners.com/cve/CVE-2019-19524 REPORT
https://vulners.com/cve/CVE-2019-19533 REPORT
https://vulners.com/cve/CVE-2019-19537 REPORT
https://vulners.com/cve/CVE-2019-19543 REPORT
https://vulners.com/cve/CVE-2019-19602 REPORT
https://vulners.com/cve/CVE-2019-19767 REPORT
https://vulners.com/cve/CVE-2019-19770 REPORT
https://vulners.com/cve/CVE-2019-20054 REPORT
https://vulners.com/cve/CVE-2019-20636 REPORT
https://vulners.com/cve/CVE-2019-9455 REPORT
https://vulners.com/cve/CVE-2019-9458 REPORT
https://vulners.com/cve/CVE-2020-0305 REPORT
https://vulners.com/cve/CVE-2020-0444 REPORT
https://vulners.com/cve/CVE-2020-10732 REPORT
https://vulners.com/cve/CVE-2020-10751 REPORT
https://vulners.com/cve/CVE-2020-10773 REPORT
https://vulners.com/cve/CVE-2020-10774 REPORT
https://vulners.com/cve/CVE-2020-10942 REPORT
https://vulners.com/cve/CVE-2020-11565 REPORT
https://vulners.com/cve/CVE-2020-11668 REPORT
https://vulners.com/cve/CVE-2020-12465 REPORT
https://vulners.com/cve/CVE-2020-12655 REPORT
https://vulners.com/cve/CVE-2020-12659 REPORT
https://vulners.com/cve/CVE-2020-12770 REPORT
https://vulners.com/cve/CVE-2020-12826 REPORT
https://vulners.com/cve/CVE-2020-14381 REPORT
https://vulners.com/cve/CVE-2020-25641 REPORT
https://vulners.com/cve/CVE-2020-8647 REPORT
https://vulners.com/cve/CVE-2020-8648 REPORT
https://vulners.com/cve/CVE-2020-8649 REPORT
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "AlmaLinux:8",
        "name": "kernel-tools-libs-devel"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.18.0-240.el8"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "The kernel packages contain the Linux kernel, the core of any Linux operating system.\n\nSecurity Fix(es):\n\n* kernel: use after free in the video driver leads to local privilege escalation (CVE-2019-9458)\n\n* kernel: use-after-free in drivers/bluetooth/hci_ldisc.c (CVE-2019-15917)\n\n* kernel: out-of-bounds access in function hclge_tm_schd_mode_vnet_base_cfg (CVE-2019-15925)\n\n* kernel: memory leak in ccp_run_sha_cmd() (CVE-2019-18808)\n\n* kernel: Denial Of Service in the __ipmi_bmc_register() (CVE-2019-19046)\n\n* kernel: out-of-bounds write in ext4_xattr_set_entry (CVE-2019-19319)\n\n* Kernel: kvm: OOB memory write via kvm_dev_ioctl_get_cpuid (CVE-2019-19332)\n\n* kernel: use-after-free in ext4_put_super (CVE-2019-19447)\n\n* kernel: a malicious USB device in the drivers/input/ff-memless.c leads to use-after-free (CVE-2019-19524)\n\n* kernel: race condition caused by a malicious USB device in the USB character device driver layer (CVE-2019-19537)\n\n* kernel: use-after-free in serial_ir_init_module() (CVE-2019-19543)\n\n* kernel: use-after-free in __ext4_expand_extra_isize and ext4_xattr_set_entry (CVE-2019-19767)\n\n* kernel: use-after-free in debugfs_remove (CVE-2019-19770)\n\n* kernel: out-of-bounds write via crafted keycode table (CVE-2019-20636)\n\n* kernel: possible use-after-free due to a race condition in cdev_get  (CVE-2020-0305)\n\n* kernel: out-of-bounds read in in vc_do_resize function (CVE-2020-8647)\n\n* kernel: use-after-free in n_tty_receive_buf_common function (CVE-2020-8648)\n\n* kernel: invalid read location in vgacon_invert_region function (CVE-2020-8649)\n\n* kernel: uninitialized kernel data leak in userspace coredumps (CVE-2020-10732)\n\n* kernel: SELinux netlink permission check bypass (CVE-2020-10751)\n\n* kernel: out-of-bounds write in mpol_parse_str  (CVE-2020-11565)\n\n* kernel: mishandles invalid descriptors in drivers/media/usb/gspca/xirlink_cit.c (CVE-2020-11668)\n\n* kernel: buffer overflow in mt76_add_fragment function (CVE-2020-12465)\n\n* kernel: xdp_umem_reg in net/xdp/xdp_umem.c has an out-of-bounds write which could result in crash and data coruption (CVE-2020-12659)\n\n* kernel: sg_write function lacks an sg_remove_request call in a certain failure case (CVE-2020-12770)\n\n* kernel: possible to send arbitrary signals to a privileged (suidroot) parent process (CVE-2020-12826)\n\n* kernel: referencing inode of removed superblock in get_futex_key() causes UAF (CVE-2020-14381)\n\n* kernel: soft-lockups in iov_iter_copy_from_user_atomic() could result in DoS (CVE-2020-25641)\n\n* kernel: kernel pointer leak due to WARN_ON statement in video driver leads to local information disclosure (CVE-2019-9455)\n\n* kernel: null pointer dereference in dlpar_parse_cc_property  (CVE-2019-12614)\n\n* kernel: null-pointer dereference in drivers/net/fjes/fjes_main.c (CVE-2019-16231)\n\n* kernel: null pointer dereference in drivers/scsi/qla2xxx/qla_os.c (CVE-2019-16233)\n\n* kernel: memory leak in  af9005_identify_state() function (CVE-2019-18809)\n\n* kernel: A memory leak in the mwifiex_pcie_alloc_cmdrsp_buf() function (CVE-2019-19056)\n\n* kernel: memory leak in the crypto_report() function (CVE-2019-19062)\n\n* kernel: Two memory leaks in the rtl_usb_probe() function (CVE-2019-19063)\n\n* kernel: A memory leak in the rtl8xxxu_submit_int_urb() function (CVE-2019-19068)\n\n* kernel: A memory leak in the predicate_parse() function (CVE-2019-19072)\n\n* kernel: information leak bug caused  by a malicious USB device in the drivers/media/usb/ttusb-dec/ttusb_dec.c (CVE-2019-19533)\n\n* kernel: Null pointer dereference in drop_sysctl_table() (CVE-2019-20054)\n\n* kernel: kernel stack information leak on s390/s390x (CVE-2020-10773)\n\n* kernel: possibility of memory disclosure when reading the file /proc/sys/kernel/rh_features (CVE-2020-10774)\n\n* kernel: vhost-net: stack overflow in get_raw_socket while checking sk_family field (CVE-2020-10942)\n\n* kernel: sync of excessive duration via an XFS v5 image with crafted metadata (CVE-2020-12655)",
  "id": "ALSA-2020:4431",
  "modified": "2021-08-11T08:54:00Z",
  "published": "2020-11-03T12:03:57Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-12614"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-15917"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-15925"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-16231"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-16233"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-18808"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-18809"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-19046"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-19056"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-19062"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-19063"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-19068"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-19072"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-19319"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-19332"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-19447"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-19524"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-19533"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-19537"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-19543"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-19602"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-19767"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-19770"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-20054"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-20636"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-9455"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2019-9458"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-0305"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-0444"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-10732"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-10751"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-10773"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-10774"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-10942"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-11565"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-11668"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-12465"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-12655"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-12659"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-12770"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-12826"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-14381"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-25641"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-8647"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-8648"
    },
    {
      "type": "REPORT",
      "url": "https://vulners.com/cve/CVE-2020-8649"
    }
  ],
  "related": [
    "CVE-2019-12614",
    "CVE-2019-15917",
    "CVE-2019-15925",
    "CVE-2019-16231",
    "CVE-2019-16233",
    "CVE-2019-18808",
    "CVE-2019-18809",
    "CVE-2019-19046",
    "CVE-2019-19056",
    "CVE-2019-19062",
    "CVE-2019-19063",
    "CVE-2019-19068",
    "CVE-2019-19072",
    "CVE-2019-19319",
    "CVE-2019-19332",
    "CVE-2019-19447",
    "CVE-2019-19524",
    "CVE-2019-19533",
    "CVE-2019-19537",
    "CVE-2019-19543",
    "CVE-2019-19602",
    "CVE-2019-19767",
    "CVE-2019-19770",
    "CVE-2019-20054",
    "CVE-2019-20636",
    "CVE-2019-9455",
    "CVE-2019-9458",
    "CVE-2020-0305",
    "CVE-2020-0444",
    "CVE-2020-10732",
    "CVE-2020-10751",
    "CVE-2020-10773",
    "CVE-2020-10774",
    "CVE-2020-10942",
    "CVE-2020-11565",
    "CVE-2020-11668",
    "CVE-2020-12465",
    "CVE-2020-12655",
    "CVE-2020-12659",
    "CVE-2020-12770",
    "CVE-2020-12826",
    "CVE-2020-14381",
    "CVE-2020-25641",
    "CVE-2020-8647",
    "CVE-2020-8648",
    "CVE-2020-8649"
  ],
  "schema_version": "1.7.0",
  "summary": "Moderate: kernel security, bug fix, and enhancement update",
  "upstream": [
    "CVE-2019-12614",
    "CVE-2019-15917",
    "CVE-2019-15925",
    "CVE-2019-16231",
    "CVE-2019-16233",
    "CVE-2019-18808",
    "CVE-2019-18809",
    "CVE-2019-19046",
    "CVE-2019-19056",
    "CVE-2019-19062",
    "CVE-2019-19063",
    "CVE-2019-19068",
    "CVE-2019-19072",
    "CVE-2019-19319",
    "CVE-2019-19332",
    "CVE-2019-19447",
    "CVE-2019-19524",
    "CVE-2019-19533",
    "CVE-2019-19537",
    "CVE-2019-19543",
    "CVE-2019-19602",
    "CVE-2019-19767",
    "CVE-2019-19770",
    "CVE-2019-20054",
    "CVE-2019-20636",
    "CVE-2019-9455",
    "CVE-2019-9458",
    "CVE-2020-0305",
    "CVE-2020-0444",
    "CVE-2020-10732",
    "CVE-2020-10751",
    "CVE-2020-10773",
    "CVE-2020-10774",
    "CVE-2020-10942",
    "CVE-2020-11565",
    "CVE-2020-11668",
    "CVE-2020-12465",
    "CVE-2020-12655",
    "CVE-2020-12659",
    "CVE-2020-12770",
    "CVE-2020-12826",
    "CVE-2020-14381",
    "CVE-2020-25641",
    "CVE-2020-8647",
    "CVE-2020-8648",
    "CVE-2020-8649"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.