CVE-2016-8636 json
Integer overflow in the mem_check_range function in drivers/infiniband/sw/rxe/rxe_mr.c in the Linux kernel before 4.9.10 allows local users…
published 2017-02-22 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-9479
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
Integer overflow in the mem_check_range function in drivers/infiniband/sw/rxe/rxe_mr.c in the Linux kernel before 4.9.10 allows local users to cause a denial of service (memory corruption), obtain sensitive information from kernel memory, or possibly have unspecified other impact via a write or read request involving the "RDMA protocol over infiniband" (aka Soft RoCE) technology.
Patch / fix
- linux linux_kernel 4.9.10
- linux Debian 14, Debian 13, Debian 12 4.9.10-1
debian advisories DEBIAN-CVE-2016-8636
- linux-hwe Ubuntu 16.04 LTS 4.10.0-32.36~16.04.1
ubuntu advisories UBUNTU-CVE-2016-8636
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-syms SLES for SAP 12 SP2, SLES 12 SP2-LTSS, SLES 12 SP2-BCL +2 more 4.4.121-92.109.2
- kernel-source SLES for SAP 12 SP2, SLES 12 SP2-LTSS, SLES 12 SP2-BCL +2 more 4.4.121-92.109.2
- kernel-default SLES for SAP 12 SP2, SLES 12 SP2-LTSS, SLES 12 SP2-BCL +3 more 4.4.121-92.109.2
- kgraft-patch-SLE12-SP2_Update_29 SLES for SAP 12 SP2, SLES 12 SP2-LTSS, OpenStack Cloud 7 +1 more 1-3.5.2
suse advisories SUSE-SU-2019:1287-1
- git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=647bf3… commit
- github.com/torvalds/linux@647bf3d commit
- bugzilla.redhat.com/show_bug.cgi?id=1421981 patch
- openwall.com/lists/oss-security/2017/02/11/9 advisory
- eyalitkin.wordpress.com/2017/02/11/cve-publication-cve-2016-8636/ advisory
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2016-8636 updated cvss 5.8
kernel: Integer overflow in the RDMA over infiniband software implementation
-
Red Hat Enterprise Linux 5 kernel Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise MRG 2 kernel-rt, mrg-rt-release, kernel-rt-trace, kernel-rt-vanilla, kernel-rt-firmwarenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-190 Integer Overflow or Wraparound
- Technology feeds
References
-
git.kernel.org
/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=647bf3d8a8e5777319da92af672289b2a6c4dc66
issue-tracking, patch, third-party-advisory
-
github.com
/torvalds/linux/commit/647bf3d8a8e5777319da92af672289b2a6c4dc66
issue-tracking, patch, third-party-advisory
-
openwall.com
/lists/oss-security/2017/02/11/9
mailing-list, patch, third-party-advisory
-
eyalitkin.wordpress.com
/2017/02/11/cve-publication-cve-2016-8636/
patch, technical-description, third-party-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=1421981
issue-tracking, patch
-
kernel.org
/pub/linux/kernel/v4.x/ChangeLog-4.9.10
release-notes, vendor-advisory
-
securityfocus.com
/bid/96189
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2016-8636
- NVD CVE-2016-8636
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.