Drivers 3079 Published by

NVIDIA shipped Linux x64 Display Driver 620.73.04 today, landing just two weeks after the R620 production branch launched. The official changelog offers only a single line: "Minor bug fixes and improvements," so NVIDIA did not confirm exactly which items were addressed. Those fixes are attributed to the branch's initial 620.70.06 build, which already patched Wayland performance, the Assassin's Creed Shadows hang, and a Final Fantasy VII Rebirth crash. NVIDIA positions R620 as the successor to the 595 series, pairing with CUDA Toolkit 13.5, and the driver is available for download now.





NVIDIA Ships 620.73.04 Linux Driver, a Quiet Point Release Closes Out R620's First Week

NVIDIA shipped Linux x64 Display Driver 620.73.04 today, landing just over two weeks after the R620 production branch opened its doors. The official changelog? A single line: "Minor bug fixes and improvements." That's the entire itemized list.

It's the kind of mid-cycle update that keeps a freshly launched driver line from stalling out, though it won't win any creativity awards. The same bi-weekly release cycle has shown up across earlier NVIDIA branches: an initial build lands, then follow-ups roll in fast to clean up whatever early users had to say.

Nvidia

Reading the version number (and what "bug fixes" might mean)

The 620 is the branch, .73 marks a new feature-set increment, and .04 is just the build number. The branch opened at .70 on November 4, which is oddly early for a production line these days, but the point stands: this is exactly the sort of targeted stability refresh you'd expect, not a feature drop.

NVIDIA didn't publish a per-fix list for 620.73.04, so where do the fixes come from at all? The branch's launch driver, 620.70.06, already ran down a long regression checklist. Wayland explicit-synchronization performance got a bump for high-frame-rate compositing, OpenGL on-screen display now works across every Vulkan backend including Wayland, and an old corruption-flickering bug in Vulkan apps under Wayland got squashed. There was also the Assassin's Creed Shadows hang, a Vulkan "device lost" regression dating back to the R595 series that had bitten Linux gamers for roughly three months.

Let's be clear on the attribution, because it matters. Those items belong to the R620 branch and its initial 620.70.06 build, not necessarily to this exact point release. Whether 620.73.04 adds new fixes or merely hardens the existing list is undocumented. The only thing NVIDIA confirmed publicly is that terse one-liner.

Keep in mind that the file itself lands at 549.73 MB, which is standard for these bundled drivers since the download ships the graphics driver alongside an optional NVIDIA App.

Installing it, and the wider R620 ecosystem

Architecture-wise the driver covers 64-bit Linux, shipped as installers for both x86_64/AMD64/EM64T and aarch64/ARM64. NVIDIA still positions R620 as the direct successor to the 595 series, so if you're sitting on an older production branch like the 580 LTSB or 570, verify GPU and distro compatibility before you poke at anything.

Many distros package their own NVIDIA builds that play nicer with the system's update machinery. NVIDIA repeats this note on basically every driver page, so you may want to hit the distro repos before falling back to the standalone .run installer. The branch also pairs with CUDA Toolkit 13.5, which ships production support targeting the next-generation Vera Rubin platform.

The driver doesn't exist in a vacuum. NVIDIA is meanwhile upstreaming a Rust-written GPU kernel module called Nova to the mainline kernel, with VGPU support on top. And a couple of security advisories have been floating around, including the NvRoot and ForgePtr vulnerabilities, with NVIDIA hinting at roughly 25 more coming down the pike. If you're on shared or remote GPUs, the ForgePtr and NvRoot ones are worth a closer look.

As for what this means for you in practice: it's a sensible stability refresh for anyone already on R620, and it keeps the branch as the current recommended production driver. Not a reason to rush an update if you're running something stable, but not a skip either. Keep an eye on the release highlights, though. if NVIDIA ever does spell out what changed, this is the page to check.

Head here to the release page.