CVE-2016-2186: Null Pointer Dereference

Published Mar 11, 2016
·
Updated

A flaw was found in in the Linux kernel's USB device management code which could cause a crash when a device which required powermate driver. The kernel would panic causing null pointer dereference attempting to access non existent endpoints.

Product bug:

https://bugzilla.redhat.com/showbug.cgi?id=1283384

Public via:

http://seclists.org/bugtraq/2016/Mar/85

This was assigned CVE-2016-2186 by Red Hat.

Other sources

The powermateprobe function in drivers/input/misc/powermate.c in the Linux kernel before 4.5.1 allows physically proximate attackers to cause a denial of service (NULL pointer dereference and system crash) via a crafted endpoints value in a USB device descriptor.

— Launchpad

Affected Software

47 affected componentsFixes available
Linux Linux kernel<=4.5.0
Novell Suse Linux Enterprise Software Development Kit=11.0-sp4
Novell Suse Linux Enterprise Software Development Kit=12.0
Novell Suse Linux Enterprise Software Development Kit=12.0-sp1
Novell Suse Linux Enterprise Debuginfo=11.0-sp4
Novell Suse Linux Enterprise Desktop=12.0
Novell Suse Linux Enterprise Desktop=12.0-sp1
Novell Suse Linux Enterprise Live Patching=12.0
Novell Suse Linux Enterprise Module For Public Cloud=12.0
Novell Suse Linux Enterprise Real Time Extension=11.0-sp4
Novell Suse Linux Enterprise Real Time Extension=12.0-sp1
Novell Suse Linux Enterprise Server=11.0-extra
Novell Suse Linux Enterprise Server=11.0-sp4
Novell Suse Linux Enterprise Server=12.0
Novell Suse Linux Enterprise Server=12.0-sp1
Novell Suse Linux Enterprise Workstation Extension=12.0
Novell Suse Linux Enterprise Workstation Extension=12.0-sp1
Canonical Ubuntu Linux=12.04
debian/linux
6.1.176-16.1.190-16.12.107-16.12.116-17.2.15-17.3.3-1
ubuntu/linux<3.13.0-86.130
3.13.0-86.130
ubuntu/linux-lts-utopic<3.16.0-71.91~14.04.1
3.16.0-71.91~14.04.1
ubuntu/linux-lts-vivid<3.19.0-59.65~14.04.1
3.19.0-59.65~14.04.1
ubuntu/linux-lts-wily<4.2.0-36.41~14.04.1
4.2.0-36.41~14.04.1
ubuntu/linux-lts-xenial<4.4.0-22.39~14.04.1
4.4.0-22.39~14.04.1
ubuntu/linux<4.4.0-22.39
4.4.0-22.39
ubuntu/linux-raspi2<4.4.0-1010.12
4.4.0-1010.12
ubuntu/linux-snapdragon<4.4.0-1013.14
4.4.0-1013.14
ubuntu/linux-azure*
ubuntu/linux-gcp*
ubuntu/linux-hwe*
ubuntu/linux-hwe-edge*
ubuntu/linux-azure-fde*
ubuntu/linux-azure-fde-5.15*
ubuntu/linux-gke*
ubuntu/linux-gkeop*
ubuntu/linux-raspi2*
ubuntu/linux-riscv*
ubuntu/linux-intel-iot-realtime*
ubuntu/linux-realtime*
ubuntu/linux-riscv*
ubuntu/linux-azure-6.11*
ubuntu/linux-gcp-6.11*
ubuntu/linux-hwe-6.11*
ubuntu/linux-lowlatency-hwe-6.11*
ubuntu/linux-raspi-realtime*
ubuntu/linux-realtime*
ubuntu/linux-riscv*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/linux to a version that resolves this vulnerability.

    Fixed in 3.13.0-86.130
  2. Upgrade

    Upgrade ubuntu/linux-lts-utopic to a version that resolves this vulnerability.

    Fixed in 3.16.0-71.91~14.04.1
  3. Upgrade

    Upgrade ubuntu/linux-lts-vivid to a version that resolves this vulnerability.

    Fixed in 3.19.0-59.65~14.04.1
  4. Upgrade

    Upgrade ubuntu/linux-lts-wily to a version that resolves this vulnerability.

    Fixed in 4.2.0-36.41~14.04.1
  5. Upgrade

    Upgrade ubuntu/linux-lts-xenial to a version that resolves this vulnerability.

    Fixed in 4.4.0-22.39~14.04.1
  6. Upgrade

    Upgrade ubuntu/linux to a version that resolves this vulnerability.

    Fixed in 4.4.0-22.39
  7. Upgrade

    Upgrade ubuntu/linux-raspi2 to a version that resolves this vulnerability.

    Fixed in 4.4.0-1010.12
  8. Upgrade

    Upgrade ubuntu/linux-snapdragon to a version that resolves this vulnerability.

    Fixed in 4.4.0-1013.14
  9. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.116-1Fixed in 7.2.15-1Fixed in 7.3.4-1
  10. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Fixed in 4.5.1

Event History

Mar 11, 2016
Data Sourced
via Red Hat·05:20 PM
DescriptionSeverityAffected Software
May 2, 2016
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2016-2186?

CVE-2016-2186 is considered a medium severity vulnerability due to potential kernel crashes.

2

How do I fix CVE-2016-2186?

To address CVE-2016-2186, update the Linux kernel to a version higher than 4.5.0 or apply the recommended patches.

3

Which products are affected by CVE-2016-2186?

CVE-2016-2186 affects various versions of the Linux kernel and specific SUSE Linux Enterprise products.

4

What type of vulnerability is CVE-2016-2186?

CVE-2016-2186 is a vulnerability in the USB device management code within the Linux kernel.

5

Can CVE-2016-2186 lead to system instability?

Yes, CVE-2016-2186 can cause a kernel panic and lead to system instability when a vulnerable USB device is connected.

Company

Resources

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