LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53750: pinctrl: freescale: Fix a memory out of bounds when num_configs is 1

In the Linux kernel, the following vulnerability has been resolved: pinctrl: freescale: Fix a memory out of bounds when num_configs is 1 The config passed in by pad wakeup is 1, when num_configs is 1, Configuration [1] should not be fetched, which will be detected by KASAN as a memory out of bounds condition. Modify to get configs[1] when num_configs is 2.

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

Security readout for executives and security teams

Plain-English summary

This CVE is a Linux kernel bug in the Freescale pin control driver. Under a specific pad wakeup configuration, the kernel may read past the provided configuration array. The sources do not provide CVSS, attacker requirements, impact beyond KASAN detection, or evidence of exploitation.

Executive priority

Treat this as a kernel maintenance priority, not an emergency, based on current evidence. Raise priority where affected embedded devices are safety-critical, hard to patch, or have reliability requirements tied to wakeup behavior.

Technical view

The flaw is in Linux kernel pinctrl/freescale handling when num_configs is 1. The vulnerable logic could fetch configs[1] even though only one configuration was supplied. Stable kernel commits change the logic so configs[1] is accessed only when num_configs is 2.

Likely exposure

Most relevant to Linux systems using the Freescale pinctrl driver, commonly embedded or NXP/Freescale ARM platforms. The source marks Linux versions including 6.2, 6.3.13, 6.4.4, and 6.5 as affected, but does not provide complete deployment context.

Exploitation context

The provided sources do not show active exploitation, public exploit availability, KEV listing, or a remote attack path. Evidence only describes a memory out-of-bounds condition detected by KASAN during pad wakeup configuration handling.

Researcher notes

Analysis is constrained by sparse public data. The CVE description identifies the faulty bounds assumption and fix direction, but not the exact vulnerable function, attack prerequisites, privilege requirements, or security impact beyond memory out-of-bounds detection.

Mitigation direction

  • Apply kernel updates containing the referenced stable fixes.
  • Check distribution or device-vendor advisories for backported kernel patches.
  • Prioritize systems using Freescale/NXP pinctrl hardware paths.
  • If patch timing is uncertain, request vendor confirmation of exposure.

Validation and detection

  • Inventory Linux kernel versions on Freescale/NXP-based systems.
  • Confirm whether the referenced stable commits are present or backported.
  • Review kernel logs for KASAN or out-of-bounds reports in pinctrl/freescale.
  • Validate patched kernels in device wakeup and suspend-resume workflows.
Prepared
Confidence
medium
Sources
5

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-53750 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
4Source 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
LinuxLinuxf60c9eac54af28d7b5651fe49944bfd5098550e6, f60c9eac54af28d7b5651fe49944bfd5098550e6, f60c9eac54af28d7b5651fe49944bfd5098550e6unaffected
LinuxLinux6.2, 0, 6.3.13, 6.4.4, 6.5affected
Weakness

CWE details

No CWE listed

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