Skip to content
Fencer Vulns
medium 5.3

CVE-2019-9836 json

Secure Encrypted Virtualization (SEV) on Advanced Micro Devices (AMD) Platform Security Processor (PSP; aka AMD Secure Processor or AMD-SP)…

published 2019-06-25 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-19196

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.6%
EPSS 1.6% chance of exploitation in 30 days, percentile 76%
public exploits
0
none known

Summary

Secure Encrypted Virtualization (SEV) on Advanced Micro Devices (AMD) Platform Security Processor (PSP; aka AMD Secure Processor or AMD-SP) 0.17 build 11 and earlier has an insecure cryptographic implementation.

Patch / fix

  • amd64-microcode Debian 14, Debian 13, Debian 12 3.20220411.1

debian advisories DEBIAN-CVE-2019-9836

  • kernel-firmware SLE Module for Basesystem 15 20190618-3.22.1
  • kernel-firmware SLES for SAP 12 SP4, SLES 12 SP4, SLED 12 SP4 20190618-5.8.1
  • kernel-firmware SLE Module for Basesystem 15 SP1 20190618-3.3.1

suse advisories SUSE-SU-2019:1803-1SUSE-SU-2019:1802-1SUSE-SU-2019:1792-1

  • kernel-firmware-all openSUSE Tumbleweed 20250206-1.1
  • kernel-firmware-amdgpu openSUSE Tumbleweed 20250206-1.1
  • kernel-firmware-ath10k openSUSE Tumbleweed 20250206-1.1
  • kernel-firmware-ath11k openSUSE Tumbleweed 20250206-1.1
  • kernel-firmware-ath12k openSUSE Tumbleweed 20250206-1.1
  • kernel-firmware-atheros openSUSE Tumbleweed 20250206-1.1
  • kernel-firmware-bluetooth openSUSE Tumbleweed 20250208-1.1
  • kernel-firmware-bnx2 openSUSE Tumbleweed 20250206-1.1

opensuse advisories openSUSE-SU-2025:14804-1openSUSE-SU-2025:14769-1openSUSE-SU-2025:14770-1openSUSE-SU-2025:14771-1openSUSE-SU-2025:14772-1openSUSE-SU-2025:14773-1

Exploit prediction

1.61% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

Sources

Fencer Vulns 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.