CVE-2023-0185
Nvidia Virtual Gpu ≤ 11.12
Raw vector
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-0185 is a medium-severity Unsigned to Signed Conversion Error (CWE-196) vulnerability in Nvidia Virtual Gpu. Its CVSS base score is 6.7 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked at the 11th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-12274
Vulnerability Data
NVIDIA GPU Display Driver for Linux contains a vulnerability in the kernel mode layer, where sign conversion issuescasting an unsigned primitive to signed may lead to denial of service or information disclosure.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices (reviews, static analysis, safe integer handling) directly prevent unsigned-to-signed conversion errors during development.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure development lifecycle mandates practices that can catch or prevent unsafe type conversions.
A.8.26 requires identifying and specifying security requirements (including resilience against attacks like buffer overflows or SQL injection) but does not itself implement any mechanism that stops an unsigned-to-signed conversion error from being present or exploited
A.8.27 mandates establishing and applying secure engineering principles (including least privilege, security by design, and design reviews) but does not itself stop an unsigned-to-signed cast error from being introduced or from being exploitable once present.
Secure coding standards directly address avoiding unsafe casts from unsigned to signed integers.