CVE-2016-10200: google android
Vulnerability summary
CVE-2016-10200 is a high (CVSS 7.0) vulnerability in google android. EPSS estimates a 0.30% chance of exploitation in the next 30 days, higher than 22.3% of scored vulnerabilities.
Not severe (CVSS 7, local access); no exploitation reported by the 5 checked sources
Source freshness unavailable
How is this decided?Advisory lineage
Upstream 0 · Downstream 13 · Related 8Timeline
- 07-03-2017PublishedVulnerability first disclosed.
- 06-08-2024Last modifiedVulnerability information updated.
Description
Race condition in the L2TPv3 IP Encapsulation feature in the Linux kernel before 4.8.14 allows local users to gain privileges or cause a denial of service (use-after-free) by making multiple bind system calls without properly ascertaining whether a socket has the SOCK_ZAPPED status, related to net/l2tp/l2tp_ip.c and net/l2tp/l2tp_ip6.c.
CVSS metrics
5 scores · 3 sources · 3 versions- OSV · UbuntuEcosystem advisory · calculated7.0HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
- OSV · DebianEcosystem advisory · calculated7.0HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS trend
Probability
0.30%
Chance of exploitation in the next 30 days
Percentile
22%
Versus all other CVEs
30-day change
No change 0.00 pp
From 0.30% on 04-10-2026
Known exploited
Compare KEV catalogs
CISA KEVNot in the CISA KEV catalog.
ENISA CNWNot in the ENISA CNW catalog.
CIRCLNot in the CIRCL catalog.
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root cause- CWE-264Permissions, Privileges, and Access ControlsWeaknesses in this category are related to the management of permissions, privileges, and other security features that are used to perform access control.
- CWE-362Concurrent Execution using Shared Resource with Improper SynchronizationThe product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
- CWE-416Use After FreeThe product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Affected systems
Known conditions: local access, low-privilege account, no user interaction (CVSS vector). Other conditions: not stated in public data.
Ubuntu6 products
- linux< 3.13.0-132.181 | < 4.4.0-62.83
- linux-aws< 4.4.0-1003.12
- linux-hwe< 4.8.0-39.42~16.04.1
- linux-lts-xenial< 4.4.0-62.83~14.04.1
- linux-raspi2< 4.4.0-1042.49
Debian1 product
- linux< 4.8.15-1
Google1 product
- android≤ 7.1.1
Linux1 product
- linux_kernel≥ 3.0.34, < 3.2 | ≥ 3.2.20, < 3.2.88 | ≥ 3.4.2, < 3.12.69 | ≥ 3.13, < 3.16.40 | ≥ 3.17, < 3.18.52 | ≥ 3.19, < 4.4.38 | ≥ 4.5, < 4.8.14
4 vendors · 9 products
References
16 links- github.com/torvalds/linux/commit/32c231164b762dddefa13af5a0101032c70b50efX Refsource CONFIRMIssue TrackingPatchThird Party AdvisoryREPORT
- www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.8.14X Refsource CONFIRMRelease NotesVendor AdvisoryREPORT
