CVE-2023-28585
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMemory corruption while loading an ELF segment in TEE Kernel.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMemory corruption vulnerability in the TEE (Trusted Execution Environment) Kernel that occurs during the loading of ELF (Executable and Linkable Format) segments. This allows an attacker to potentially execute arbitrary code or cause a denial of service in the trusted execution environment.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Qualcomm firmware productCheck your device firmware version or system information to determine if you are using any of the affected products: Qualcomm 315 5G IoT Modem, Qualcomm 9205 LTE Modem, Qualcomm Aqt1000, Qualcomm Ar8031, Qualcomm Ar8035, Qualcomm C-V2X 9150, Qualcomm Csr8811, or Qualcomm Csra6620Affected if The device runs any of the listed firmware products and the TEE is enabled
-
Check if TEE is enabledExamine system configuration or debug interfaces to determine if the Trusted Execution Environment is active. This may be accessible via AT commands, diagnostic logs, or system configuration files depending on the deviceAffected if TEE is enabled and ELF loading capabilities are present in the trusted environment
-
Verify ELF loading capability in TEEReview the TEE kernel configuration or memory layout to determine if ELF segment loading functionality is exposed. Check for any debug or diagnostic interfaces that may allow loading ELF binaries into the TEEAffected if ELF loading functionality is available and accessible in the trusted execution environment
-
Review TEE memory corruption indicatorsCheck TEE crash logs, error dumps, or memory corruption reports for symptoms occurring during ELF segment processing. Look for unexpected resets or stability issues attributed to the TEE subsystemAffected if Memory corruption or unexpected TEE crashes occur during ELF-related operations
-
Check for unpatched TEE kernelCompare the installed TEE kernel version or build date against vendor release notes or security advisories for CVE-2023-28585 patchesAffected if The TEE kernel is unpatched and ELF loading is enabled
A user is affected if their device runs one of the listed Qualcomm firmware products with TEE enabled and ELF segment loading capability available in the trusted execution environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the vendor-specific patch for the TEE kernel implementation. If no patch is available, consider disabling untrusted ELF loading capabilities or restricting the attack surface that can trigger ELF segment loading.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28585 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-28585 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data