Ubuntu 4208-1: Linux kernel vulnerabilities

    Date 02 Dec 2019
    731
    Posted By LinuxSecurity Advisories
    Several security issues were fixed in the Linux kernel.
    ==========================================================================
    Ubuntu Security Notice USN-4208-1
    December 02, 2019
    
    linux, linux-aws, linux-gcp, linux-gcp-5.3, linux-kvm, linux-oracle
    vulnerabilities
    ==========================================================================
    
    A security issue affects these releases of Ubuntu and its derivatives:
    
    - Ubuntu 19.10
    - Ubuntu 18.04 LTS
    
    Summary:
    
    Several security issues were fixed in the Linux kernel.
    
    Software Description:
    - linux: Linux kernel
    - linux-aws: Linux kernel for Amazon Web Services (AWS) systems
    - linux-gcp: Linux kernel for Google Cloud Platform (GCP) systems
    - linux-kvm: Linux kernel for cloud environments
    - linux-oracle: Linux kernel for Oracle Cloud systems
    - linux-gcp-5.3: Linux kernel for Google Cloud Platform (GCP) systems
    
    Details:
    
    Jann Horn discovered that the OverlayFS and ShiftFS Drivers in the Linux
    kernel did not properly handle reference counting during memory mapping
    operations when used in conjunction with AUFS. A local attacker could use
    this to cause a denial of service (system crash) or possibly execute
    arbitrary code. (CVE-2019-15794)
    
    Nicolas Waisman discovered that the WiFi driver stack in the Linux kernel
    did not properly validate SSID lengths. A physically proximate attacker
    could use this to cause a denial of service (system crash).
    (CVE-2019-17133)
    
    It was discovered that the ARM Komeda display driver for the Linux kernel
    did not properly deallocate memory in certain error conditions. A local
    attacker could use this to cause a denial of service (memory exhaustion).
    (CVE-2019-18810)
    
    It was discovered that the VirtualBox guest driver implementation in the
    Linux kernel did not properly deallocate memory in certain error
    conditions. A local attacker could use this to cause a denial of service
    (memory exhaustion). (CVE-2019-19048)
    
    It was discovered that the ADIS16400 IIO IMU Driver for the Linux kernel
    did not properly deallocate memory in certain error conditions. A local
    attacker could use this to cause a denial of service (memory exhaustion).
    (CVE-2019-19060, CVE-2019-19061)
    
    It was discovered that the Intel OPA Gen1 Infiniband Driver for the Linux
    kernel did not properly deallocate memory in certain error conditions. A
    local attacker could use this to cause a denial of service (memory
    exhaustion). (CVE-2019-19065)
    
    It was discovered that the AMD Audio CoProcessor Driver for the Linux
    kernel did not properly deallocate memory in certain error conditions. A
    local attacker with the ability to load modules could use this to cause a
    denial of service (memory exhaustion). (CVE-2019-19067)
    
    It was discovered in the Qualcomm FastRPC Driver for the Linux kernel did
    not properly deallocate memory in certain error conditions. A local
    attacker could use this to cause a denial of service (memory exhaustion).
    (CVE-2019-19069)
    
    It was discovered that the Cascoda CA8210 SPI 802.15.4 wireless controller
    driver for the Linux kernel did not properly deallocate memory in certain
    error conditions. A local attacker could use this to cause a denial of
    service (memory exhaustion). (CVE-2019-19075)
    
    It was discovered that the AMD Display Engine Driver in the Linux kernel
    did not properly deallocate memory in certain error conditions. A local
    attack could use this to cause a denial of service (memory exhaustion).
    (CVE-2019-19083)
    
    Nicolas Waisman discovered that the Chelsio T4/T5 RDMA Driver for the Linux
    kernel performed DMA from a kernel stack. A local attacker could use this
    to cause a denial of service (system crash). (CVE-2019-17075)
    
    Update instructions:
    
    The problem can be corrected by updating your system to the following
    package versions:
    
    Ubuntu 19.10:
      linux-image-5.3.0-1007-oracle   5.3.0-1007.8
      linux-image-5.3.0-1008-aws      5.3.0-1008.9
      linux-image-5.3.0-1008-kvm      5.3.0-1008.9
      linux-image-5.3.0-1009-gcp      5.3.0-1009.10
      linux-image-5.3.0-24-generic    5.3.0-24.26
      linux-image-5.3.0-24-generic-lpae  5.3.0-24.26
      linux-image-5.3.0-24-lowlatency  5.3.0-24.26
      linux-image-5.3.0-24-snapdragon  5.3.0-24.26
      linux-image-aws                 5.3.0.1008.10
      linux-image-gcp                 5.3.0.1009.10
      linux-image-generic             5.3.0.24.28
      linux-image-generic-lpae        5.3.0.24.28
      linux-image-gke                 5.3.0.1009.10
      linux-image-kvm                 5.3.0.1008.10
      linux-image-lowlatency          5.3.0.24.28
      linux-image-oracle              5.3.0.1007.8
      linux-image-snapdragon          5.3.0.24.28
      linux-image-virtual             5.3.0.24.28
    
    Ubuntu 18.04 LTS:
      linux-image-5.3.0-1009-gcp      5.3.0-1009.10~18.04.1
      linux-image-gcp-edge            5.3.0.1009.9
    
    After a standard system update you need to reboot your computer to make
    all the necessary changes.
    
    ATTENTION: Due to an unavoidable ABI change the kernel updates have
    been given a new version number, which requires you to recompile and
    reinstall all third party kernel modules you might have installed.
    Unless you manually uninstalled the standard kernel metapackages
    (e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual,
    linux-powerpc), a standard system upgrade will automatically perform
    this as well.
    
    References:
      https://usn.ubuntu.com/4208-1
      CVE-2019-15794, CVE-2019-17075, CVE-2019-17133, CVE-2019-18810,
      CVE-2019-19048, CVE-2019-19060, CVE-2019-19061, CVE-2019-19065,
      CVE-2019-19067, CVE-2019-19069, CVE-2019-19075, CVE-2019-19083
    
    Package Information:
      https://launchpad.net/ubuntu/+source/linux/5.3.0-24.26
      https://launchpad.net/ubuntu/+source/linux-aws/5.3.0-1008.9
      https://launchpad.net/ubuntu/+source/linux-gcp/5.3.0-1009.10
      https://launchpad.net/ubuntu/+source/linux-kvm/5.3.0-1008.9
      https://launchpad.net/ubuntu/+source/linux-oracle/5.3.0-1007.8
      https://launchpad.net/ubuntu/+source/linux-gcp-5.3/5.3.0-1009.10~18.04.1
    

    LinuxSecurity Poll

    If you are using full-disk encryption: are you concerned about the resulting performance hit?

    No answer selected. Please try again.
    Please select either existing option or enter your own, however not both.
    Please select minimum 0 answer(s) and maximum 2 answer(s).
    /main-polls/34-if-you-are-using-full-disk-encryption-are-you-concerned-about-the-resulting-performance-hit?task=poll.vote&format=json
    34
    radio
    [{"id":"120","title":"Yes","votes":"13","type":"x","order":"1","pct":65,"resources":[]},{"id":"121","title":"No ","votes":"7","type":"x","order":"2","pct":35,"resources":[]}] ["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"] ["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"] 350
    bottom 200

    Please enable / Bitte aktiviere JavaScript!
    Veuillez activer / Por favor activa el Javascript![ ? ]

    We use cookies to provide and improve our services. By using our site, you consent to our Cookie Policy.