CVE-2016-8650

Name: CVE-2016-8650
Creator: NVD / NIST
Published: 2016-11-28T03:59:09.843+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 0.41%

Last modified Jun 17, 2026

CVE-2016-8650 is a vulnerability of currently unknown severity. The mpi_powm function in lib/mpi/mpi-pow.c in the Linux kernel through 4.8.11 does not ensure that memory is allocated for limb data, which allows local users to cause a denial of service (stack memory corruption and panic) via an add_key system call for an RSA key with a zero exponent.. EPSS estimates a 0.41% chance of exploitation in the next 30 days.

Description

The mpi_powm function in lib/mpi/mpi-pow.c in the Linux kernel through 4.8.11 does not ensure that memory is allocated for limb data, which allows local users to cause a denial of service (stack memory corruption and panic) via an add_key system call for an RSA key with a zero exponent.

Metrics

EPSS Probability

0.41%

32.3th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

Vendor	Product	Versions
Linux	Linux Kernel	<= 4.8.11

References

http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f5527fffff3f002b0a6b376163613b82f69de073Issue Tracking, Patch, Vendor Advisory
http://seclists.org/fulldisclosure/2016/Nov/76Mailing List
http://www.openwall.com/lists/oss-security/2016/11/24/8Mailing List, Third Party Advisory
http://www.securityfocus.com/bid/94532
http://www.securitytracker.com/id/1037968
https://access.redhat.com/errata/RHSA-2017:0931
https://access.redhat.com/errata/RHSA-2017:0932
https://access.redhat.com/errata/RHSA-2017:0933
https://access.redhat.com/errata/RHSA-2018:1854
https://bugzilla.redhat.com/show_bug.cgi?id=1395187Issue Tracking
https://github.com/torvalds/linux/commit/f5527fffff3f002b0a6b376163613b82f69de073Issue Tracking, Patch, Third Party Advisory
https://source.android.com/security/bulletin/2017-03-01.html
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f5527fffff3f002b0a6b376163613b82f69de073Issue Tracking, Patch, Vendor Advisory
http://seclists.org/fulldisclosure/2016/Nov/76Mailing List
http://www.openwall.com/lists/oss-security/2016/11/24/8Mailing List, Third Party Advisory
http://www.securityfocus.com/bid/94532
http://www.securitytracker.com/id/1037968
https://access.redhat.com/errata/RHSA-2017:0931
https://access.redhat.com/errata/RHSA-2017:0932
https://access.redhat.com/errata/RHSA-2017:0933
https://access.redhat.com/errata/RHSA-2018:1854
https://bugzilla.redhat.com/show_bug.cgi?id=1395187Issue Tracking
https://github.com/torvalds/linux/commit/f5527fffff3f002b0a6b376163613b82f69de073Issue Tracking, Patch, Third Party Advisory
https://source.android.com/security/bulletin/2017-03-01.html

Timeline

Published: Nov 28, 2016
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2016-8650?

How severe is CVE-2016-8650?

Severity scoring for CVE-2016-8650 is pending analysis. The EPSS model estimates a 0.41% probability of exploitation in the next 30 days.

How do I fix CVE-2016-8650?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-8650?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST