CVE-2015-7892 json
Stack-based buffer overflow in the m2m1shot_compat_ioctl32 function in the Samsung m2m1shot driver framework, as used in Samsung S6 Edge, a…
published 2019-12-09 6 y ago modified 2026-06-17 4 mo ago also EUVD-2015-7790
- cvss
- 7.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 71%
- public exploits
- 1
- Exploit-DB
Summary
Stack-based buffer overflow in the m2m1shot_compat_ioctl32 function in the Samsung m2m1shot driver framework, as used in Samsung S6 Edge, allows local users to have unspecified impact via a large data.buf_out.num_planes value in an ioctl call.
Timeline
- First public exploit (EDB-38555)
- Published
Exploit prediction
1.35% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-38555 Samsung - 'm2m1shot' Kernel Driver Buffer Overflow dos, 2015-10-28
- packetstormsecurity.com http://packetstormsecurity.com/files/134108/Samsung-M2m1shot-Kernel-Driver-Buffer-Overflow.html referenced PoC, tagged "exploit" by a source, unverified
- code.google.com https://code.google.com/p/google-security-research/issues/detail?id=493 referenced PoC, tagged "exploit" by a source, unverified
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 | 4.6 | AV:L/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
packetstormsecurity.com
/files/134108/Samsung-M2m1shot-Kernel-Driver-Buffer-Overflow.html
exploit, third-party-advisory, vdb-entry
-
code.google.com
/p/google-security-research/issues/detail?id=493
exploit, third-party-advisory
-
exploit-db.com
/exploits/38555/
exploit, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2015-7892
- NVD CVE-2015-7892
Fencer Intel 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.