In FreeBSD before 11.2-STABLE(r343782), 11.2-RELEASE-p9, 12.0-STABLE(r343781), and 12.0-RELEASE-p3, kernel callee-save registers are not pr…

published 2019-02-12 7y ago modified 2026-06-17 4mo ago also EUVD-2019-15170

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

In FreeBSD before 11.2-STABLE(r343782), 11.2-RELEASE-p9, 12.0-STABLE(r343781), and 12.0-RELEASE-p3, kernel callee-save registers are not properly sanitized before return from system calls, potentially allowing some kernel data used in the system call to be exposed.

Patch / fix

links 1

security.freebsd.org/advisories/FreeBSD-SA-19:01.syscall.asc advisory

Is CVE-2019-5595 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

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

CVSS scores

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

Affected products

FreeBSD FreeBSD

Classification

Weakness

CWE-459 Incomplete Cleanup

References

security.freebsd.org /advisories/FreeBSD-SA-19:01.syscall.asc
vendor-advisory, patch
exchange.xforce.ibmcloud.com /vulnerabilities/156624
third-party-advisory

Sources

CVE List CVE-2019-5595
NVD CVE-2019-5595

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.