LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54049: rpmsg: glink: Add check for kstrdup

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel reliability flaw in the rpmsg GLINK component. If a memory allocation fails, the kernel code could dereference a NULL pointer instead of returning an error. The available sources do not provide a CVSS score, CWE, confirmed exploitability, or active exploitation evidence.

Executive priority

Treat as a kernel maintenance item unless GLINK-enabled systems are business-critical or unstable. There is no cited active exploitation, but kernel crashes can still affect device availability and service reliability.

Technical view

The fix adds a check for kstrdup() failure in rpmsg: glink and returns an error to avoid a NULL pointer dereference. The CVE source lists Linux as affected across kernel branch versions and provides stable kernel commit references for fixes.

Likely exposure

Exposure is most relevant to Linux systems that include or use the rpmsg GLINK driver. This commonly matters more for kernels built for supported hardware using that subsystem. The source bundle does not identify specific distributions, devices, or configurations.

Exploitation context

The bundle does not show KEV listing, public exploitation, or weaponized details. The described failure mode is a NULL pointer dereference after allocation failure, which generally suggests availability risk, but practical reachability is not established by the provided sources.

Researcher notes

Evidence is limited to the CVE record description and kernel stable commit references. No CVSS, CWE, exploit status, distribution advisory, or configuration-specific impact details are included in the supplied bundle.

Mitigation direction

  • Apply the relevant Linux stable kernel fix or vendor kernel update.
  • Prioritize systems with rpmsg GLINK enabled or required by hardware.
  • Check distribution or device vendor advisories for packaged fixed kernel versions.
  • Avoid inventing local workarounds; follow kernel or vendor guidance.

Validation and detection

  • Inventory running kernel versions against the affected version data.
  • Confirm whether rpmsg GLINK is built in or loadable on target kernels.
  • Verify vendor kernel packages include one of the referenced stable fixes.
  • Review crash logs for NULL pointer dereference symptoms in rpmsg GLINK paths.
Prepared
Confidence
medium
Sources
11

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54049 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
10Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb4f8e52b89f69f5563ac4cb9ffdacc4418917af1, b4f8e52b89f69f5563ac4cb9ffdacc4418917af1, b4f8e52b89f69f5563ac4cb9ffdacc4418917af1, b4f8e52b89f69f5563ac4cb9ffdacc4418917af1, b4f8e52b89f69f5563ac4cb9ffdacc4418917af1, b4f8e52b89f69f5563ac4cb9ffdacc4418917af1, b4f8e52b89f69f5563ac4cb9ffdacc4418917af1, b4f8e52b89f69f5563ac4cb9ffdacc4418917af1, b4f8e52b89f69f5563ac4cb9ffdacc4418917af1unaffected
LinuxLinux4.13, 0, 4.14.326, 4.19.295, 5.4.257, 5.10.195, 5.15.132, 6.1.53, 6.4.16, 6.5.3, 6.6affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.