Security Resilience

CVE-2023-31082

Linux Kernel 6.2

Published
24 April 2023
Modified
21 November 2024
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0036 28th percentile
Risk Priority 43 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-31082 is a medium-severity Release of Invalid Pointer or Reference (CWE-763) vulnerability in Linux Linux Kernel. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked at the 28th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

An issue was discovered in drivers/tty/n_gsm.c in the Linux kernel 6.2. There is a sleeping function called from an invalid context in gsmld_write, which will block the kernel. Note: This has been disputed by 3rd parties as not a valid…

more

vulnerability.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
T1003.006 DCSync Credential Access
Adversaries may attempt to access credentials and other sensitive information by abusing a Windows Domain Controller's application programming interface (API)(Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft GetNCCChanges) (Citati…
T1006 Direct Volume Access Stealth
Adversaries may directly access a volume to bypass file access controls and file system monitoring.
T1010 Application Window Discovery Discovery
Adversaries may attempt to get a listing of open application windows.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-56573Same product: Linux Linux Kernel
CVE-2024-50057Same product: Linux Linux Kernel
CVE-2024-35832Same product: Linux Linux Kernel
CVE-2024-38617Same product: Linux Linux Kernel
CVE-2024-36890Same product: Linux Linux Kernel
CVE-2026-63986Same product: Linux Linux Kernel
CVE-2023-0459Same product: Linux Linux Kernel
CVE-2024-42132Same product: Linux Linux Kernel
CVE-2026-46189Same product: Linux Linux Kernel
CVE-2024-40979Same product: Linux Linux Kernel

Affected Assets

linux
linux kernel
6.2

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.

PR.PS-06 partial match
blocks

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.

blocks

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.

blocks

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.

blocks

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.

prevents

Secure coding standards directly prohibit mismatched or incorrect pointer-release calls.

finds

Security testing can detect invalid pointer releases before release.

References