← Search results
CVE-LINKED INVENTORY38 SECURITY RECORDS
Nvidia Corporation
Android
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at android, but registry activity is not a publisher support boundary.
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-2018-6271 | 13 Feb 2019 | n/a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-6268 | 13 Feb 2019 | n/a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-6267 | 13 Feb 2019 | n/a | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-6241 | 31 Jan 2019 | N/A | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-6254 | 10 May 2018 | NA | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2018-6246 | 10 May 2018 | NA | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-6293 | 10 May 2018 | NA | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2017-6289 | 10 May 2018 | NA | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2017-6288 | 12 Mar 2018 | NA | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-6287 | 12 Mar 2018 | NA | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-6286 | 12 Mar 2018 | NA | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-6285 | 12 Mar 2018 | NA | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-6281 | 12 Mar 2018 | NA | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-6280 | 6 Mar 2018 | NA | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-6279 | 6 Feb 2018 | NA | 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-2017-6258 | 6 Feb 2018 | NA | 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-2017-6276 | 6 Dec 2017 | NA | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-6263 | 6 Dec 2017 | NA | 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-2017-6262 | 6 Dec 2017 | NA | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-6264 | 14 Nov 2017 | N/A | 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-2017-0340 | 7 Jul 2017 | NA | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-0326 | 7 Jul 2017 | NA | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-6247 | 6 Jul 2017 | NA | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-0339 | 5 Apr 2017 | Kernel-3.10 | 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-2017-0332 | 5 Apr 2017 | Kernel-3.10 | 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-2017-0330 | 5 Apr 2017 | Kernel-3.10 | 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-2017-0329 | 5 Apr 2017 | Kernel-3.18 | 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-2017-0328 | 5 Apr 2017 | Kernel-3.10 | 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-2017-0327 | 5 Apr 2017 | Kernel-3.10 | 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-2017-0325 | 5 Apr 2017 | Kernel-3.10, Kernel-3.18 | 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-2017-0338 | 8 Mar 2017 | Kernel-3.18 | 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-2017-0337 | 8 Mar 2017 | Kernel-3.18 | 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-2017-0336 | 8 Mar 2017 | Kernel-3.18 | 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-2017-0335 | 8 Mar 2017 | Kernel-3.18 | 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-2017-0334 | 8 Mar 2017 | Kernel-3.18 | 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-2017-0333 | 8 Mar 2017 | Kernel-3.18 | 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-2017-0307 | 8 Mar 2017 | Kernel-3.18 | 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-2017-0306 | 8 Mar 2017 | Kernel-3.10 | 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.