BSD Ports

x11/nvidia-driver-304 304.137_11 MidnightBSD

System
MidnightBSD
Repository
mports
Maintainer
[email protected]
Last update
Commit
a05ee84a11
Categories

Description

In the other systems

The newest version among them is 304.137, as upstream numbers it.

SystemPortVersionVulnerabilitiesStatusMaintainerLast update
MidnightBSDx11/nvidia-driver-304304.137_11 newestno data-[email protected]2026-08-05
FreeBSDx11/nvidia-driver-304304.137_12 newestnone known-[email protected]2026-09-21
HardenedBSDx11/nvidia-driver-304304.137_12 newestno data-[email protected]-
GhostBSDx11/nvidia-driver-304304.137_11 newestno data-[email protected]-

Install

Binary package:

mport install -304

From mports:

cd /usr/mports/x11/nvidia-driver-304 && make install clean

To depend on this port in another port's Makefile:

RUN_DEPENDS=	-304>0:x11/nvidia-driver-304

Dependencies

No port depends on this one.

Files

distinfo 2
FileSizeSHA256
NVIDIA-FreeBSD-x86_64-304.137.tar.gz3.6474676e+07231693189e1bdf5c1dd02315cde5ef9ed6c0854564314438f2f40f9788a34120
NVIDIA-FreeBSD-x86-304.137.tar.gz3.5399011e+075f874133853eacc5b9a10311cec22d3c4898db7f75b92bb6c12d5be5126516fb

Commit history 1

DateCommitCreditsLog message
a05ee84a11 Lucas Holt x11/nvidia-driver: add CPE identifier so mport audit can see it
mport audit matches installed packages against sec.midnightbsd.org by CPE, and these packages shipped an empty cpe field, so audit could not report NVIDIA driver vulnerabilities at any version. NVD files the driver as nvidia:gpu_driver rather than by the port name, which is why a name-based sweep does not find it; the identifier is taken from the FreeBSD port, which has carried it for some time. There are 127 CVEs recorded against it. Setting this in the master port covers the legacy slave ports too, each with its own version. Checked against the audit API: 390.157 56 CVEs 470.256.02 6 CVEs 580.126.09 0 CVEs (current branch is clean) PORTREVISION bumped on the master and on each slave so the rebuilt packages pick up the metadata. …