Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Tuesday May 14 2019, @04:30PM   Printer-friendly
from the does-this-also-affect-Android? dept.

Submitted via IRC for AnonymousLuser:

Linux Kernel Prior to 5.0.8 Vulnerable to Remote Code Execution

Linux machines running distributions powered by kernels prior to 5.0.8 are affected by a race condition vulnerability leading to a use after free, related to net namespace cleanup, exposing vulnerable systems to remote attacks.

Potential attackers could exploit the security flaw found in Linux kernel's rds_tcp_kill_sock TCP/IP implementation in net/rds/tcp.c to trigger denial-of-service (DoS) states and to execute code remotely on vulnerable Linux machines.

The attacks can be launched with the help of specially crafted TCP packets sent to vulnerable Linux boxes which can trigger use-after-free errors and enable the attackers to execute arbitrary code on the target system.

The remotely exploitable vulnerability has been assigned a 8.1 high severity base score by NIST's NVD, it is being tracked as CVE-2019-11815 (Red Hat, Ubuntu, SUSE, and Debian) and it could be abused by unauthenticated attackers without interaction from the user.

Luckily, because the attack complexity is high, the vulnerability received an exploitability score of 2.2 while the impact score is limited to 5.9.

[...] The Linux kernel developers issued a patch for the CVE-2019-11815 issue during late-March and fixed the flaw in the Linux kernel 5.0.8 version released on April 17.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by Gaaark on Tuesday May 14 2019, @06:32PM (1 child)

    by Gaaark (41) on Tuesday May 14 2019, @06:32PM (#843528) Journal

    sudo manjaro-settings-manager

    Install 5.09-2

    Reboot

    Living the dream. It's got the changelog there and all.

    --
    --- Please remind me if I haven't been civil to you: I'm channeling MDC. ---Gaaark 2.0 ---
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 1, Interesting) by Anonymous Coward on Tuesday May 14 2019, @09:15PM

    by Anonymous Coward on Tuesday May 14 2019, @09:15PM (#843591)

    I have unstable repos enabled and given them a low pin priority. I'm using testing, which everyone says you shouldn't and I agree (from a security perspective).

    The issue is fixed in 4.19.37-1 in Sid, so all I had to do was: apt-get -t unstable install linux-image

    $ cat /etc/apt/sources.list.d/unstable.list

    deb http://ftp.se.debian.org/debian/ unstable main contrib non-free
    deb-src http://ftp.se.debian.org/debian/ unstable main contrib non-free

    $ cat /etc/apt/preferences.d/pins
    # Packages from local repository on harddrive
    Package: *
    Pin: origin ""
    Pin-Priority: 1001

    # Packages from distro
    Package: *
    Pin: release a=buster
    Pin-Priority: 900

    # Packages from unstable
    Package: *
    Pin: release a=unstable
    Pin-Priority: 600