CVE-2023-53729
Description
In the Linux kernel, the following vulnerability has been resolved:
soc: qcom: qmi_encdec: Restrict string length in decode
The QMI TLV value for strings in a lot of qmi element info structures account for null terminated strings with MAX_LEN + 1. If a string is actually MAX_LEN + 1 length, this will cause an out of bounds access when the NULL character is appended in decoding.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Linux kernel QMI decoder lacks a bounds check on string length, causing an out-of-bounds access when decoding a maximum-length null-terminated string.
Root
Cause
The vulnerability resides in the Qualcomm MSM (QMI) encode/decode helper (qmi_encdec) within the Linux kernel's soc subsystem. The QMI TLV (Type-Length-Value) elements define string fields with a maximum length, and many element info structures account for the null terminator by using a buffer of MAX_LEN + 1. However, the decode logic does not verify that the incoming string length is strictly less than MAX_LEN + 1 before appending a null character. If a string is exactly MAX_LEN + 1 bytes long, the null terminator write will access one byte beyond the allocated buffer, triggering an out-of-bounds write [1][2][3].
Exploitation & Attack Surface
No special privileges are required to trigger this bug locally; it can be reached through any code path that decodes a QMI message containing a string field of maximum length. An attacker with the ability to send crafted QMI messages—for example, through a netlink socket or a Qualcomm IPC channel—can deliberately set a string field to its maximum permitted length to provoke the out-of-bounds condition. No authentication is needed if the interface is accessible from userspace, making this a local privilege escalation vector [1][2][3].
Impact
Successful exploitation leads to a kernel-stack buffer overflow, which can corrupt adjacent stack data. An attacker may leverage this to overwrite a return address or other critical kernel structures, ultimately achieving arbitrary code execution in the kernel context. This can result in a full system compromise, including privilege escalation and denial of service (system crash) [1][2][3].
Mitigation & Status
The fix has been applied in upstream Linux kernel releases following the identification of the bug. Stable kernel updates contain the patch that adds a proper length check before appending the null terminator. System administrators should apply the latest stable kernel updates from their distribution. No workaround is available short of updating the kernel [1][2][3].
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
76b58859e7c4a64c5e916fabe2ccab9f82772b2f39b813d1ef6250ecb7fbb22ee7c9c7f388d207400fd6bVulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
7- git.kernel.org/stable/c/22ee7c9c7f381be178b4457bc54530002e08e938nvd
- git.kernel.org/stable/c/2ccab9f82772ead618689d17dbc6950d6bd1e741nvd
- git.kernel.org/stable/c/64c5e916fabe5ef7bef0210b8a59fa8941ee1b8envd
- git.kernel.org/stable/c/6b58859e7c4ac357517a59f0801e8ce1b58a8ee2nvd
- git.kernel.org/stable/c/8d207400fd6b79c92aeb2f33bb79f62dff904ea2nvd
- git.kernel.org/stable/c/b2f39b813d1eed4a522428d1e6acd7dfe9b81579nvd
- git.kernel.org/stable/c/f6250ecb7fbb934b89539e7e2ba6c1d8555c0975nvd
News mentions
0No linked articles in our index yet.