Mageia 2019-0333: kernel-linus security update

    Date 19 Nov 2019
    671
    Posted By LinuxSecurity Advisories
    This kernel-linus update is based on the upstream 5.3.13 and fixes atleast the following security issues: Insufficient access control in a subsystem for Intel (R) processor graphics may allow an authenticated user to potentially enable escalation of
    MGASA-2019-0333 - Updated kernel-linus packages fix security vulnerabilities
    
    Publication date: 19 Nov 2019
    URL: https://advisories.mageia.org/MGASA-2019-0333.html
    Type: security
    Affected Mageia releases: 7
    CVE: CVE-2019-0155,
         CVE-2019-1125,
         CVE-2019-10207,
         CVE-2019-11135,
         CVE-2018-12207,
         CVE-2019-14814,
         CVE-2019-14815,
         CVE-2019-14816,
         CVE-2019-14821,
         CVE-2019-14835,
         CVE-2019-16714,
         CVE-2019-17666
    
    This kernel-linus update is based on the upstream 5.3.13 and fixes atleast
    the following security issues:
    
    Insufficient access control in a subsystem for Intel (R) processor graphics
    may allow an authenticated user to potentially enable escalation of
    privilege via local access (CVE-2019-0155).
    
    A Spectre SWAPGS gadget was found in the Linux kernel's implementation of
    system interrupts. An attacker with local access could use this information
    to reveal private data through a Spectre like side channel (CVE-2019-1125).
    
    A flaw was found in the Linux kernel’s Bluetooth implementation of UART.
    An attacker with local access and write permissions to the Bluetooth
    hardware could use this flaw to issue a specially crafted ioctl function
    call and cause the system to crash (CVE-2019-10207).
    
    TSX Asynchronous Abort condition on some CPUs utilizing speculative
    execution may allow an authenticated user to potentially enable
    information disclosure via a side channel with local access
    (CVE-2019-11135).
    
    Improper invalidation for page table updates by a virtual guest operating
    system for multiple Intel(R) Processors may allow an authenticated user to
    potentially enable denial of service of the host system via local access
    (CVE-2018-12207). 
    
    For proper mitigations and fixes for theese issues, a microcode update is
    also needed, either with a bios/uefi update from your hardware vendor or
    by installing the microcode-0.20191112-1.mga7.nonfree update (mga#25688).
    
    There is heap-based buffer overflow in the marvell wifi chip driver that
    allows local users to cause a denial of service(system crash) or possibly
    execute arbitrary code (CVE-2019-14814, CVE-2019-14815, CVE-2019-14816).
    
    An out-of-bounds access issue was found 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' and 'ring->last' value could be supplied by a host
    user-space process. An unprivileged host user or process with access to
    '/dev/kvm' device could use this flaw to crash the host kernel, resulting
    in a denial of service or potentially escalating privileges on the system
    (CVE-2019-14821).
    
    A buffer overflow flaw was found 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 host when migration is underway,
    could use this flaw to increase their privileges on the host
    (CVE-2019-14835).
    
    In the Linux kernel before 5.2.14, rds6_inc_info_copy in net/rds/recv.c
    allows attackers to obtain sensitive information from kernel stack memory
    because tos and flags fields are not initialized (CVE-2019-16714)
    
    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-17666)
    
    For other upstream fixes in this update, see the referenced changelogs.
    
    References:
    - https://bugs.mageia.org/show_bug.cgi?id=25687
    - https://bugs.mageia.org/show_bug.cgi?id=25688
    - https://kernelnewbies.org/Linux_5.2
    - https://kernelnewbies.org/Linux_5.3
    - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.1
    - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.2
    - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.3
    - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.4
    - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.5
    - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.6
    - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.7
    - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.8
    - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.9
    - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.10
    - https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.11
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0155
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1125
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10207
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11135
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12207
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14814
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14815
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14816
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14821
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14835
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16714
    - https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17666
    
    SRPMS:
    - 7/core/kernel-linus-5.3.11-1.mga7
    

    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":59.09,"resources":[]},{"id":"121","title":"No ","votes":"9","type":"x","order":"2","pct":40.91,"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

    Advisories

    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.