An issue was discovered on Samsung mobile devices with KK(4.4), L(5.0/5.1), and M(6.0) (with Hrm sensor support) software
Published Apr 7, 2020
8.1
HIGHCVSS 3.1
EPSS 0.31%
Description
An issue was discovered on Samsung mobile devices with KK(4.4), L(5.0/5.1), and M(6.0) (with Hrm sensor support) software. The sysfs of the MAX86902 sensor driver does not prevent concurrent access, leading to a race condition and resultant heap-based buffer overflow. The Samsung ID is SVE-2016-7341 (December 2016).
Affected products
Remediation
No remediation recorded yet.
Metrics
No CVSS v4.0 score for this CVE.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
No CVSS v3.0 score for this CVE.
AV:N/AC:M/Au:N/C:P/I:P/A:P
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2022–2026- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Percentile over time
- EPSS v2
- EPSS v3
- EPSS v4
- EPSS v5
Table of values (10 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 0.31% (0.00307) | 21.25th | v5 (v2026.06.15) |
| Jun 15, 2026 | 0.31% (0.00307) | 22.13th | v5 (v2026.06.15) |
| Mar 17, 2025 | 0.12% (0.00123) | 28.97th | v4 (v2025.03.14) |
| Dec 12, 2024 | 0.12% (0.00119) | 47.72th | v3 (v2023.03.01) |
| Jun 14, 2024 | 0.12% (0.00119) | 46.33th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.12% (0.00119) | 44.29th | v3 (v2023.03.01) |
| Mar 6, 2023 | 0.89% (0.00885) | 27.89th | v2 (v2022.01.01) |
| Sep 10, 2022 | 0.89% (0.00885) | 26.24th | v2 (v2022.01.01) |
| Apr 1, 2022 | 0.89% (0.00885) | 24.24th | v2 (v2022.01.01) |
| Feb 4, 2022 | 0.89% (0.00885) | 10.50th | v2 (v2022.01.01) |
References (1)
- https://security.samsungmobile.com/securityUpdate.smsb x_refsource_CONFIRMVendor Advisory
| Link | Providers | Tags |
|---|---|---|
| https://security.samsungmobile.com/securityUpdate.smsb | x_refsource_CONFIRMVendor Advisory |
Change history (0)
No recorded changes yet.