CVE-2015-8709: High severity linux kernel vulnerability

Published Jan 4, 2016
·
Updated

DISPUTED kernel/ptrace.c in the Linux kernel through 4.4.1 mishandles uid and gid mappings, which allows local users to gain privileges by establishing a user namespace, waiting for a root process to enter that namespace with an unsafe uid or gid, and then using the ptrace system call. NOTE: the vendor states "there is no kernel bug here."

Other sources

Linux kernel built with the User Namespaces(CONFIGUSERNS) support is vulnerable to a potential privilege escalation flaw. It could occur when a root owned process tries to enter a user namespace, wherein a user attempts to attach the entering process via ptrace(1).

A privileged name space user could use this flaw to potentially escalate their privileges on the system.

Upstream fix: ------------- -> https://lkml.org/lkml/2015/12/25/71

Reference: ---------- -> http://seclists.org/oss-sec/2015/q4/614

Red Hat

Affected Software

2 affected componentsFixes available
Linux Linux kernel<=4.4.1
debian/linux
5.10.223-15.10.234-16.1.129-16.1.133-16.12.21-16.12.22-1

Event History

Jan 4, 2016
Data Sourced
via Red Hat·06:14 AM
DescriptionSeverityAffected Software
Feb 8, 2016
CVE Published
via MITRE·02:00 AM
Data Sourced
via MITRE·02:00 AM
Description
Disputed
03:59 AM
Jan 11, 2024
Data Sourced
via Launchpad·10:13 PM
Description
Sep 16, 2024
Data Sourced
via Ubuntu·01:10 AM
RemedyDescriptionSeverityAffected Software
Mar 27, 2025
Data Sourced
via Debian·03:20 AM
DescriptionAffected Software

Frequently Asked Questions

1

What is the vulnerability ID for this issue?

CVE-2015-8709.

2

What is the severity level of CVE-2015-8709?

The severity level of CVE-2015-8709 is high.

3

How does CVE-2015-8709 affect the Linux kernel?

CVE-2015-8709 allows local users to gain privileges by exploiting a mishandling of uid and gid mappings in the Linux kernel.

4

Which Linux kernel versions are affected by CVE-2015-8709?

Linux kernel versions through 4.4.1 are affected by CVE-2015-8709.

5

Is there a fix available for CVE-2015-8709?

Yes, the remedy is to upgrade to the specified versions: 3.13.0-103.150, 4.10~, 3.19.0-75.83, 4.2.0-22.27, 4.4.0-51.72, 4.8.0-28.30, and others.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203