← Search results
CVE-LINKED INVENTORY840 SECURITY RECORDS
Samsung Mobile
Samsung Mobile devices
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2022-26093 | 11 Apr 2022 | Q(10), R(11), S(12) < SMR Apr-2022 Release 1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-26092 | 11 Apr 2022 | Q(10), R(11), S(12) < SMR Apr-2022 Release 1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-26091 | 11 Apr 2022 | Q(10), R(11), S(12) < SMR Apr-2022 Release 1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-25833 | 11 Apr 2022 | Q(10), R(11) < SMR Apr-2022 Release 1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-25832 | 11 Apr 2022 | Select Q(10), R(11), S(12) devices < SMR Apr-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-25831 | 11 Apr 2022 | Select Q(10), R(11), S(12) devices < SMR Apr-2022 Release 1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-25822 | 8 Mar 2022 | Select Q(10), R(11), S(12) devices with Exynos and Qualcomm chipsets < SMR Mar-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-25821 | 8 Mar 2022 | Q(10), R(11), S(12) devices with Exynos CP chipsets < SMR Mar-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-25820 | 8 Mar 2022 | Select R(11), S(12) devices < SMR Mar-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-25818 | 8 Mar 2022 | S(12) < SMR Mar-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-25817 | 8 Mar 2022 | Q(10), R(11) < SMR Mar-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-25816 | 8 Mar 2022 | Q(10), R(11), S(12) < SMR Mar-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-25815 | 8 Mar 2022 | Q(10), R(11) < SMR Mar-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-25814 | 8 Mar 2022 | R(11), S(12) < SMR Mar-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-24932 | 8 Mar 2022 | Q(10), R(11), S(12) < SMR Mar-2022 Release 1; - < 5.1.0.8 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-24931 | 8 Mar 2022 | Q(10), R(11) < SMR Mar-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-24929 | 8 Mar 2022 | Q(10), R(11), S(12) < SMR Mar-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-24928 | 8 Mar 2022 | R(11) < SMR Mar-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-24925 | 11 Feb 2022 | - < Android S(12) | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-24001 | 11 Feb 2022 | - < Android S(12) | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2022-24000 | 11 Feb 2022 | Q(10), R(11), S(12) < SMR Feb-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-23999 | 11 Feb 2022 | Q(10), R(11), S(12) < SMR Feb-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-23429 | 11 Feb 2022 | P(9.0), Q(10.0), R(11.0) < SMR Feb-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-23427 | 11 Feb 2022 | Q(10), R(11), S(12) < SMR Feb-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-23426 | 11 Feb 2022 | P(9.0), Q(10.0), R(11.0) < SMR Feb-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-23425 | 11 Feb 2022 | P(9.0), Q(10.0), R(11.0), S(12.0) with select Exynos devices < SMR Feb-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-22292 | 11 Feb 2022 | Q(10.0), R(11.0), S(12.0) < SMR Feb-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-22291 | 11 Feb 2022 | Q(10.0), R(11.0), S(12.0) < SMR Feb-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-22271 | 7 Jan 2022 | P(9.0), Q(10.0), R(11.0) < SMR Jan-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-22270 | 7 Jan 2022 | P(9.0), Q(10.0), R(11.0) < SMR Jan-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-22269 | 7 Jan 2022 | P(9.0), Q(10.0), R(11.0) < SMR Jan-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-22272 | 7 Jan 2022 | Q(10.0), R(11.0), S(12.0) < SMR Jan-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-22267 | 7 Jan 2022 | P(9.0), Q(10.0), R(11.0), S(12.0) < SMR Jan-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-22268 | 7 Jan 2022 | P(9.0), Q(10.0), R(11.0), S(12.0) < SMR Jan-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-22264 | 7 Jan 2022 | Q(10.0), R(11.0), S(12.0) < SMR Jan-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-22266 | 7 Jan 2022 | P(9.0), Q(10.0), R(11.0) < SMR Jan-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2022-22263 | 7 Jan 2022 | R(11.0) < SMR Jan-2022 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-25519 | 8 Dec 2021 | P(9.0), Q(10.0), R(11.0) < SMR Dec-2021 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-25518 | 8 Dec 2021 | P(9.0), Q(10.0), R(11.0) devices with selected Exynos chipsets < SMR Dec-2021 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-25517 | 8 Dec 2021 | Q(10.0), R(11.0) devices with selected Exynos chipsets < SMR Dec-2021 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-25516 | 8 Dec 2021 | P(9.0), Q(10.0), R(11.0) devices with selected Exynos chipsets < SMR Dec-2021 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-25515 | 8 Dec 2021 | P(9.0), Q(10.0), R(11.0) < SMR Dec-2021 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-25514 | 8 Dec 2021 | Q(10.0), R(11.0) < SMR Dec-2021 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-25513 | 8 Dec 2021 | Select R(11.0) devices < SMR Dec-2021 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-25512 | 8 Dec 2021 | P(9.0), Q(10.0), R(11.0) < SMR Dec-2021 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-25511 | 8 Dec 2021 | P(9.0), Q(10.0), R(11.0) < SMR Dec-2021 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-25510 | 8 Dec 2021 | P(9.0), Q(10.0), R(11.0) < SMR Dec-2021 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-25503 | 5 Nov 2021 | Select O(8.1), P(9.0), Q(10.0), R(11.0) devices with Exynos chipsets < SMR Nov-2021 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-25502 | 5 Nov 2021 | O(8.1), P(9.0), Q(10.0), R(11.0) < SMR Nov-2021 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2021-25501 | 5 Nov 2021 | Q(10.0), R(11.0) < SMR Nov-2021 Release 1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.