LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53729: soc: qcom: qmi_encdec: Restrict string length in decode

In the Linux kernel, the following vulnerability has been resolved: soc: qcom: qmi_encdec: Restrict string length in decode The QMI TLV value for strings in a lot of qmi element info structures account for null terminated strings with MAX_LEN + 1. If a string is actually MAX_LEN + 1 length, this will cause an out of bounds access when the NULL character is appended in decoding.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a bounds-checking flaw in Qualcomm QMI string decoding. A specially sized string can make the decoder write or access past the intended buffer when adding a null terminator. Business urgency depends on whether affected Linux kernels and Qualcomm QMI components are present.

Executive priority

Handle through normal kernel vulnerability management unless Qualcomm QMI-enabled systems are business-critical or exposed through higher-risk interfaces. No source provided here supports emergency treatment.

Technical view

The flaw is in soc: qcom: qmi_encdec. QMI TLV string element definitions often reserve MAX_LEN + 1 for null termination; decoding a string already that long can trigger out-of-bounds access when the decoder appends the null byte.

Likely exposure

Exposure is limited to Linux kernels containing the Qualcomm QMI encoder/decoder path and affected versions identified by the CVE record. The bundle does not identify affected distributions, devices, configurations, or whether this path is reachable remotely.

Exploitation context

The source bundle does not cite active exploitation, public exploit availability, KEV inclusion, privilege requirements, or attack vector. Treat exploitability as unproven from the provided evidence, not impossible.

Researcher notes

Evidence supports an out-of-bounds access during QMI TLV string decode. Missing details include CVSS, CWE, exploitability, reachable interfaces, exact fixed release mapping, and downstream vendor impact.

Mitigation direction

  • Update affected Linux kernels using vendor packages or stable fixes referencing this CVE.
  • Check Linux distribution advisories for backported fixes before relying on upstream version numbers.
  • Prioritize systems that enable Qualcomm QMI-related kernel functionality.
  • Track CVE and kernel stable updates for refined impact or fixed-version details.

Validation and detection

  • Inventory Linux kernel versions across affected fleets.
  • Confirm whether kernels include the soc qcom qmi_encdec code path.
  • Verify vendor kernel packages include the referenced stable commit fix.
  • Document systems where Qualcomm QMI functionality is absent or disabled.
Prepared
Confidence
medium
Sources
9

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-53729 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
8Source 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
LinuxLinux9b8a11e82615274d4133aab3cf5aa1c59191f0a2, 9b8a11e82615274d4133aab3cf5aa1c59191f0a2, 9b8a11e82615274d4133aab3cf5aa1c59191f0a2, 9b8a11e82615274d4133aab3cf5aa1c59191f0a2, 9b8a11e82615274d4133aab3cf5aa1c59191f0a2, 9b8a11e82615274d4133aab3cf5aa1c59191f0a2, 9b8a11e82615274d4133aab3cf5aa1c59191f0a2unaffected
LinuxLinux4.16, 0, 4.19.295, 5.4.257, 5.10.195, 5.15.132, 6.1.54, 6.5.4, 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.