CVE-2023-54049
Description
In the Linux kernel, the following vulnerability has been resolved:
rpmsg: glink: Add check for kstrdup
Add check for the return value of kstrdup() and return the error if it fails in order to avoid NULL pointer dereference.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A missing return-value check for kstrdup() in the Linux kernel's rpmsg glink driver could lead to a NULL pointer dereference.
Vulnerability
In the Linux kernel's rpmsg glink driver, the function kstrdup() is called without checking its return value. If memory allocation fails, kstrdup() returns NULL, and the subsequent use of this pointer without validation can lead to a NULL pointer dereference [1][2][3].
Exploitation
An attacker would need to trigger a memory allocation failure in the kernel, which could be achieved by exhausting system memory or through other means that cause kstrdup() to fail. The vulnerability is in the rpmsg glink driver, which is used for inter-processor communication in systems like Qualcomm platforms. Exploitation requires the ability to trigger the vulnerable code path, which may involve sending crafted rpmsg messages or other interactions with the driver.
Impact
A successful NULL pointer dereference can cause a kernel crash (denial of service). In some configurations, it might be exploitable for privilege escalation if the dereference occurs in a context where an attacker can control the subsequent memory access, but the primary impact is system instability.
Mitigation
The fix adds a check for the return value of kstrdup() and returns an error if it fails, preventing the NULL pointer dereference. The patch has been applied to the stable kernel branches as indicated by the referenced commits [1][2][3]. Users should update their kernels to include this fix.
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
1Patches
95197498c902513928a837e0fefa7f31669f071ac2ffd7f80abd740db896bcae0787e408c174cf8853857e3734a9558afb5c9ee8296a3Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
9- git.kernel.org/stable/c/13928a837e0f014dac0322dd9f8a67c486e7f232nvd
- git.kernel.org/stable/c/174cf8853857c190a3c4f1f1d2d06cfd095fe859nvd
- git.kernel.org/stable/c/5197498c902502127a47abda5359dd7f1d41946fnvd
- git.kernel.org/stable/c/71ac2ffd7f80fdd350486f6645dc48456e55a59bnvd
- git.kernel.org/stable/c/abd740db896b3c588dced175af98b95852c1854bnvd
- git.kernel.org/stable/c/b5c9ee8296a3760760c7b5d2e305f91412adc795nvd
- git.kernel.org/stable/c/cae0787e408c30a575760a531ccb69a6b48bbfafnvd
- git.kernel.org/stable/c/e3734a9558afac91df3c655a6f2376b9d14933b7nvd
- git.kernel.org/stable/c/efa7f31669f04084ed5996ed467ba529f4c90467nvd
News mentions
0No linked articles in our index yet.