CVE-2023-0459
Linux Kernel ≤ 4.14.307
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-0459 is a medium-severity Release of Invalid Pointer or Reference (CWE-763) vulnerability in Linux Linux Kernel. Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked at the 49th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-12513
Vulnerability Data
Copy_from_user on 64-bit versions of the Linux kernel does not implement the __uaccess_begin_nospec allowing a user to bypass the "access_ok" check and pass a kernel pointer to copy_from_user(). This would allow an attacker to leak information. We recommend upgrading beyond…
more
commit 74e19ef0ff8061ef55957c3abd71614ef0f42f47
- 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 directly prevent invalid pointer release 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.
A.8.25 mandates a secure-SDLC process (requirements, checkpoints, secure coding guidelines, testing, training) but does not itself stop an invalid pointer/reference from being released; the coding defect can still be written, reach production, and be exploitable.
A.8.26 only requires that security requirements (including resilience against attacks such as buffer overflows) be identified and specified during development; it does not itself enforce, implement or assure those requirements, so the invalid-pointer weakness can still arise and be exploited.
A.8.27 mandates establishing and applying secure engineering principles (e.g. least privilege, security by design, hardening) during architecture and development; it does not stop an invalid pointer release from being exploitable once the coding error exists in the product.
Secure coding standards directly prohibit mismatched or incorrect pointer-release calls.
Security testing can detect invalid pointer releases before release.