kernel: bnep_add_connection does not check if l2cap socket is available allowing privilege escalation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-1200-1 | linux security update |
Debian DSA |
DSA-4082-1 | linux security update |
EUVD |
EUVD-2017-7290 | The bnep_add_connection function in net/bluetooth/bnep/core.c in the Linux kernel before 3.19 does not ensure that an l2cap socket is available, which allows local users to gain privileges via a crafted application. |
Ubuntu USN |
USN-3583-1 | Linux kernel vulnerabilities |
Ubuntu USN |
USN-3583-2 | Linux kernel (Trusty HWE) vulnerabilities |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.434% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.