Kernel fault via unchecked channel-name allocation
Published Dec 24, 2025 · Updated Dec 24, 2025
NULL-pointer dereference in the Linux Qualcomm GLINK RPMsg driver allows attackers to trigger a kernel fault during channel allocation. The qcom_glink_alloc_channel function stores the result of kstrdup in channel->name and previously continued without checking for allocation failure. Reachability requires an active Qualcomm GLINK RPMsg path and a failed channel-name allocation; public records do not establish attacker control or whether the fault becomes an oops or panic.
Summary
What happened
NULL-pointer dereference in the Linux Qualcomm GLINK RPMsg driver allows attackers to trigger a kernel fault during channel allocation. The qcom_glink_alloc_channel function stores the result of kstrdup in channel->name and previously continued without checking for allocation failure. Reachability requires an active Qualcomm GLINK RPMsg path and a failed channel-name allocation; public records do not establish attacker control or whether the fault becomes an oops or panic.
The record
- CVE
- CVE-2023-54049
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.13
- Affected versionversion=b4f8e52b89f69f5563ac4cb9ffdacc4418917af1 <13928a837e0f014dac0322dd9f8a67c486e7f232
- Affected versionversion=b4f8e52b89f69f5563ac4cb9ffdacc4418917af1 <174cf8853857c190a3c4f1f1d2d06cfd095fe859
- Affected versionversion=b4f8e52b89f69f5563ac4cb9ffdacc4418917af1 <5197498c902502127a47abda5359dd7f1d41946f
- Affected versionversion=b4f8e52b89f69f5563ac4cb9ffdacc4418917af1 <71ac2ffd7f80fdd350486f6645dc48456e55a59b
- Affected versionversion=b4f8e52b89f69f5563ac4cb9ffdacc4418917af1 <abd740db896b3c588dced175af98b95852c1854b
- Affected versionversion=b4f8e52b89f69f5563ac4cb9ffdacc4418917af1 <b5c9ee8296a3760760c7b5d2e305f91412adc795
- Affected versionversion=b4f8e52b89f69f5563ac4cb9ffdacc4418917af1 <cae0787e408c30a575760a531ccb69a6b48bbfaf
- Affected versionversion=b4f8e52b89f69f5563ac4cb9ffdacc4418917af1 <e3734a9558afac91df3c655a6f2376b9d14933b7
- Affected versionversion=b4f8e52b89f69f5563ac4cb9ffdacc4418917af1 <efa7f31669f04084ed5996ed467ba529f4c90467
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo