CVE-2025-39787: soc: qcom: mdt_loader: Ensure we don't read past the ELF header
In the Linux kernel, the following vulnerability has been resolved:
soc: qcom: mdt_loader: Ensure we don't read past the ELF header
When the MDT loader is used in remoteproc, the ELF header is sanitized
beforehand, but that's not necessary the case for other clients.
Validate the size of the firmware buffer to ensure that we don't read
past the end as we iterate over the header. e_phentsize and e_shentsize
are validated as well, to ensure that the assumptions about step size in
the traversal are valid.
Security readout for executives and security teams
Plain-English summary
A Linux Qualcomm firmware loader can read beyond the available ELF header when another component supplies an insufficiently validated firmware buffer. This is a local, low-complexity vulnerability requiring low privileges. The supplied CVSS score is 7.8, but the source bundle does not establish a specific exploitation outcome beyond the unsafe read.
Executive priority
Treat this as a high-priority kernel remediation for exposed Qualcomm-based systems, particularly multi-user and managed-device fleets. It is not presently an internet-facing emergency: exploitation is local, and the supplied evidence does not show active attacks. Require owners to confirm affectedness and schedule a vendor-fixed kernel promptly.
Technical view
The qcom MDT loader iterates ELF program and section headers. Some remoteproc paths sanitize the header first, while other clients may not. The fix validates the firmware-buffer length and checks e_phentsize and e_shentsize before traversal. The CVSS assessment rates confidentiality, integrity, and availability impacts high, although the description only directly confirms an out-of-bounds read.
Likely exposure
Exposure is most likely on Linux systems using the Qualcomm MDT loader through clients that do not sanitize ELF headers beforehand. The bundle marks Linux 4.11 and multiple releases through 6.17 affected. Exact exposure depends on kernel configuration, loader use, distribution packaging, and vendor backports; the supplied version mapping is not sufficiently precise for version-only decisions.
Exploitation context
The CVSS vector indicates a local attacker with low privileges, low complexity, and no user interaction. The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation or a public exploit. Absence from KEV does not prove exploitation is impossible.
Researcher notes
The key boundary is whether a caller can provide a truncated or inconsistent ELF/MDT buffer without prior sanitization. Review all qcom MDT loader callers, not only remoteproc. The bundle supplies no CWE, proof of exploitability, crash signature, or affected configuration matrix. Do not infer code execution solely from the CVSS impact fields.
Mitigation direction
Apply a vendor or distribution kernel update containing the applicable stable fix.
Confirm the update adds firmware-buffer bounds checks and validates ELF entry sizes.
Follow device-vendor guidance for embedded or appliance kernels that may use backported fixes.
If patching is deferred, reduce untrusted local access; no product-specific workaround is supplied.
Validation and detection
Inventory Qualcomm-based Linux systems and determine whether the qcom MDT loader is built or loaded.
Record kernel package builds and compare them with vendor advisories, including documented backports.
Verify source or package metadata includes the applicable stable commit or equivalent validation changes.
Test legitimate firmware-loading workflows after updating and investigate loader errors or regressions.
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-2025-39787 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
2ADP providers
13Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.