In FreeBSD 12.0-STABLE before r349628, 12.0-RELEASE before 12.0-RELEASE-p7, 11.3-PRERELEASE before r349629, 11.3-RC3 before 11.3-RC3-p1, an…

published 2019-07-03 7y ago modified 2026-06-17 4mo ago also EUVD-2019-15177

cvss: 8.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 4.0%; EPSS 4.0% chance of exploitation in 30 days, percentile 90%
public exploits: 0; none known

In FreeBSD 12.0-STABLE before r349628, 12.0-RELEASE before 12.0-RELEASE-p7, 11.3-PRERELEASE before r349629, 11.3-RC3 before 11.3-RC3-p1, and 11.2-RELEASE before 11.2-RELEASE-p11, a bug in the cdrom driver allows users with read access to the cdrom device to arbitrarily overwrite kernel memory when media is present thereby allowing a malicious user in the operator group to gain root privileges.

Is CVE-2019-5602 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

4.02% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	8.8	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	9.0	AV:N/AC:L/Au:S/C:C/I:C/A:C

Affected products

FreeBSD FreeBSD

Classification

Weakness

CWE-787 Out-of-bounds Write
CWE-863 Incorrect Authorization

References

security.freebsd.org /advisories/FreeBSD-SA-19:11.cd_ioctl.asc
vendor-advisory
packetstormsecurity.com /files/153522/FreeBSD-Security-Advisory-FreeBSD-SA-19-11.cd_ioctl.html
third-party-advisory, vdb-entry

Sources

CVE List CVE-2019-5602
NVD CVE-2019-5602

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.