CVE-2019-15239
Last modified
CVE-2019-15239 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.59% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | 4.16.12 |
| Debian | Debian Linux | 9.0 |
| Debian | Debian Linux | 10.0 |
References
- https://pulsesecurity.co.nz/advisories/linux-kernel-4.9-tcpsocketsuafExploit, Third Party Advisory
- https://www.debian.org/security/2019/dsa-4497Third Party Advisory
- https://pulsesecurity.co.nz/advisories/linux-kernel-4.9-tcpsocketsuafExploit, Third Party Advisory
- https://www.debian.org/security/2019/dsa-4497Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2019-15239?
How severe is CVE-2019-15239?
How do I fix CVE-2019-15239?
Are you affected by CVE-2019-15239?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
