NVIDIA R555-Linux (NFB) · Version Status

NVIDIA R555-Linux (NFB) End of Life Date

NVIDIA R555-Linux (NFB) end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

NVIDIA R555-Linux (NFB) is past end of life. This version no longer receives security patches. 479 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 1, 2025
479 days past EOL
Latest Release
555.58.02
Standard release
Release Date
Jun 4, 2024
NVIDIA R555-Linux (NFB) series
Lifecycle detail

NVIDIA r555-linux was released on June 4, 2024 and support ended on June 1, 2025 — a supported lifespan of 1 year, in line with the 1 year median for NVIDIA releases. It was not an LTS release; NVIDIA reserves longer patch windows for its LTS versions. The last patch it will ever receive is 555.58.02, published July 1, 2024 — 11 months before support ended. It has been without security patches for 1 year and 4 months. 12 newer NVIDIA releases have shipped since.

← NVIDIA R550-Linux (PB) All NVIDIA versions NVIDIA R555-Windows (NFB) →
55 / 100
High Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
35/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
10/10 None available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
Recommended upgrade path
NVIDIA R615-Windows (NFB)
Latest release: 616.92 · EOL: Sep 9, 2027
View full NVIDIA timeline →
All NVIDIA Versions
VersionLatestEOL DateStatus
R390-Linux LTS 390.157 Nov 22, 2022 EOL
R390-Windows LTS 392.68 Oct 26, 2021 EOL
R418-Linux LTS 418.197.02 Mar 1, 2022 EOL
R418-Windows LTS 427.45 Mar 1, 2022 EOL
R450-Linux LTS 450.248.02 Jul 1, 2023 EOL
R450-Windows LTS 454.23 Jul 1, 2023 EOL
R460-Windows (PB) 463.15 Jan 1, 2022 EOL
R460-Linux (PB) 460.106.00 Jan 1, 2022 EOL

What does NVIDIA R555-Linux (NFB) end of life mean?

When NVIDIA R555-Linux (NFB) reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running NVIDIA R555-Linux (NFB) past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to NVIDIA R615-Windows (NFB) or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does NVIDIA R555-Linux (NFB) reach end of life?
NVIDIA R555-Linux (NFB) reached end of life on June 1, 2025. This version is no longer receiving security patches.
Is NVIDIA R555-Linux (NFB) still supported?
No. NVIDIA R555-Linux (NFB) reached end of life on June 1, 2025 and is no longer receiving security patches.
What should I upgrade to from NVIDIA R555-Linux (NFB)?
The recommended upgrade from NVIDIA R555-Linux (NFB) is NVIDIA R615-Windows (NFB) — the latest actively supported version. Check the NVIDIA full timeline for all supported versions.
What are the security risks of running NVIDIA R555-Linux (NFB) past EOL?
When NVIDIA R555-Linux (NFB) reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL NVIDIA should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →