Your submission was sent successfully! Close

You have successfully unsubscribed! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates about Ubuntu and upcoming events where you can meet our team.Close

CVE-2019-15239

Publication date 20 August 2019

Last updated 24 July 2024

Ubuntu priority

Medium

Why this priority?

Cvss 3 Severity Score

7.8 · High

Score breakdown

In the Linux kernel, a certain net/ipv4/tcp_output.c change, which was properly incorporated into 4.16.12, was incorrectly backported to the earlier longterm kernels, introducing a new vulnerability that was potentially more severe than the issue that was intended to be fixed by backporting. Specifically, by adding to a write queue between disconnection and re-connection, a local attacker can trigger multiple use-after-free conditions. This can result in a kernel crash, or potentially in privilege escalation. NOTE: this affects (for example) Linux distributions that use 4.9.x longterm kernels before 4.9.190 or 4.14.x longterm kernels before 4.14.139.

Read the notes from the security team

Status

Package Ubuntu Release Status
linux 19.04 disco
Not affected
18.04 LTS bionic
Not affected
16.04 LTS xenial
Fixed 4.4.0-165.193
14.04 LTS trusty Ignored
linux-aws 19.04 disco
Not affected
18.04 LTS bionic
Not affected
16.04 LTS xenial
Fixed 4.4.0-1095.106
14.04 LTS trusty Ignored
linux-aws-hwe 19.04 disco Not in release
18.04 LTS bionic Not in release
16.04 LTS xenial
Not affected
14.04 LTS trusty Not in release
linux-azure 19.04 disco
Not affected
18.04 LTS bionic
Not affected
16.04 LTS xenial
Not affected
14.04 LTS trusty Ignored
linux-azure-edge 19.04 disco Not in release
18.04 LTS bionic
Not affected
16.04 LTS xenial
Not affected
14.04 LTS trusty Not in release
linux-gcp 19.04 disco
Not affected
18.04 LTS bionic
Not affected
16.04 LTS xenial
Not affected
14.04 LTS trusty Not in release
linux-gcp-edge 19.04 disco Not in release
18.04 LTS bionic
Not affected
16.04 LTS xenial Not in release
14.04 LTS trusty Not in release
linux-gke-4.15 19.04 disco Not in release
18.04 LTS bionic
Not affected
16.04 LTS xenial Not in release
14.04 LTS trusty Not in release
linux-gke-5.0 19.04 disco Not in release
18.04 LTS bionic
Not affected
16.04 LTS xenial Not in release
14.04 LTS trusty Not in release
linux-hwe 19.04 disco Not in release
18.04 LTS bionic
Not affected
16.04 LTS xenial
Not affected
14.04 LTS trusty Not in release
linux-hwe-edge 19.04 disco Not in release
18.04 LTS bionic
Not affected
16.04 LTS xenial
Not affected
14.04 LTS trusty Not in release
linux-kvm 19.04 disco
Not affected
18.04 LTS bionic
Not affected
16.04 LTS xenial
Fixed 4.4.0-1059.66
14.04 LTS trusty Not in release
linux-lts-trusty 19.04 disco Not in release
18.04 LTS bionic Not in release
16.04 LTS xenial Not in release
14.04 LTS trusty Not in release
linux-lts-xenial 19.04 disco Not in release
18.04 LTS bionic Not in release
16.04 LTS xenial Not in release
14.04 LTS trusty Ignored
linux-oem 19.04 disco
Not affected
18.04 LTS bionic
Not affected
16.04 LTS xenial Ignored
14.04 LTS trusty Not in release
linux-oracle 19.04 disco
Not affected
18.04 LTS bionic
Not affected
16.04 LTS xenial
Not affected
14.04 LTS trusty Not in release
linux-raspi2 19.04 disco
Not affected
18.04 LTS bionic
Not affected
16.04 LTS xenial
Fixed 4.4.0-1123.132
14.04 LTS trusty Not in release
linux-snapdragon 19.04 disco
Not affected
18.04 LTS bionic
Not affected
16.04 LTS xenial
Fixed 4.4.0-1127.135
14.04 LTS trusty Not in release

Notes

sbeattie

This vulnerability was introduced when 7f582b248d0a86bae5788c548d7bb5bca6f7691a was incorrectly backported to stable kernels; the upstream kernel was prevented from being vulnerable because 75c119afe14f74b4dd967d75ed9f57ab6c0ef045 had landed prior to it. Thus, for the upstream kernel, the fix for the issue predates the commit that introduced the issue. link to xenial kernel git commit above demonstrates the fix that landed to address backport kernels.

Patch details

For informational purposes only. We recommend not to cherry-pick updates. How can I get the fixes?

Package Patch details
linux

Severity score breakdown

Parameter Value
Base score 7.8 · High
Attack vector Local
Attack complexity Low
Privileges required Low
User interaction None
Scope Unchanged
Confidentiality High
Integrity impact High
Availability impact High
Vector CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H