CVE-2023-54049: 
Linux Kernel vulnerability analysis and mitigation

CVE-2023-54049 is a NULL pointer dereference vulnerability in the Linux kernel's rpmsg: glink subsystem, caused by a missing return value check for kstrdup(). If kstrdup() fails due to memory allocation failure, the code proceeds with a NULL pointer, potentially leading to a kernel crash. The vulnerability affects Linux kernel versions starting from commit b4f8e52b89f6 and was published on December 24, 2025. Patched versions include 4.14.326, 4.19.295, 5.4.257, 5.10.195, 5.15.132, 6.1.53, 6.4.16, 6.5.3, and 6.6+. No CVSS score has been officially assigned at this time (Feedly, ENISA EUVD).

The root cause is a missing NULL check after calling kstrdup() in the rpmsg GLINK (Generic Link) driver (drivers/rpmsg/qcom_glink_native.c), classified as CWE-476 (NULL Pointer Dereference). When the kernel's memory allocator fails to duplicate a string — for example, under low-memory conditions — kstrdup() returns NULL, and the subsequent use of that pointer without validation causes a kernel NULL pointer dereference. Exploitation requires the ability to trigger the relevant code path in the GLINK driver, typically requiring local access or control over inter-processor communication (IPC) channels on systems using Qualcomm GLINK (common in ARM/mobile platforms). The fix adds an explicit NULL check on the return value of kstrdup() and propagates the error appropriately (Feedly, ENISA EUVD).

Successful exploitation of this vulnerability can cause a kernel NULL pointer dereference, resulting in a kernel panic (system crash) and denial of service. The primary impact is on availability; confidentiality and integrity impacts are considered low, as the vulnerability does not directly expose data or allow code execution under typical conditions. Systems using Qualcomm GLINK-based IPC (common in embedded, mobile, and ARM-based Linux platforms) are most at risk (Feedly).

Apply the relevant upstream Linux kernel patches for your kernel branch: 4.14.326, 4.19.295, 5.4.257, 5.10.195, 5.15.132, 6.1.53, 6.4.16, 6.5.3, or 6.6+. Distribution-specific updates (e.g., SUSE kernel updates SUSE-2026-0281-1 and SUSE-2026-20876-1) are also available and should be applied promptly. No configuration-based workaround is known; upgrading to a patched kernel version is the recommended remediation (Feedly, Linux Security SUSE).