LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54101: driver: soc: xilinx: use _safe loop iterator to avoid a use after free

In the Linux kernel, the following vulnerability has been resolved: driver: soc: xilinx: use _safe loop iterator to avoid a use after free The hash_for_each_possible() loop dereferences "eve_data" to get the next item on the list. However the loop frees eve_data so it leads to a use after free. Use hash_for_each_possible_safe() instead.

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory-safety flaw in the Xilinx SoC driver. A loop can free an item and then still use it while moving to the next item. The public record does not provide CVSS scoring or evidence of exploitation, so urgency depends on whether affected kernels and Xilinx SoC driver code are present.

Executive priority

Moderate tracking priority unless affected Xilinx SoC Linux systems are business-critical. No active exploitation is cited, but kernel memory-safety defects can have high impact when reachable.

Technical view

The issue is a use-after-free in driver/soc/xilinx logic using hash_for_each_possible(). The loop frees eve_data, then the iterator dereferences it to advance. The resolved change replaces the iterator with hash_for_each_possible_safe() in stable kernel fixes.

Likely exposure

Exposure appears limited to Linux systems running affected kernel code with the Xilinx SoC driver built or loaded. The source bundle lists Linux kernel impact beginning around 5.17 and stable fixes including 6.1.39, 6.3.13, 6.4.4, and 6.5.

Exploitation context

The source bundle does not cite active exploitation, public exploit availability, CVSS, CWE, or attack prerequisites. KEV status is false. Treat this as a kernel memory-corruption issue requiring inventory validation rather than an internet-wide emergency based on current evidence.

Researcher notes

The evidence is narrowly technical: a specific iterator use-after-free fixed by switching to the safe hash iterator. The bundle lacks reachability analysis, privilege requirements, crash impact, or exploitability assessment.

Mitigation direction

  • Update to a kernel containing the listed stable fixes.
  • Follow Linux distribution or vendor kernel advisories for packaged updates.
  • Prioritize Xilinx SoC systems or kernels enabling the affected driver.
  • If updates are delayed, consult vendor guidance for supported compensating controls.

Validation and detection

  • Inventory kernel versions across Linux assets.
  • Check whether the Xilinx SoC driver is built, loaded, or used.
  • Confirm the relevant stable commit is present in deployed kernel source or packages.
  • Track distribution advisories for backported fixes that may not change version numbers.
Prepared
Confidence
medium
Sources
6

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-54101 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
5Source 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
LinuxLinuxc7fdb2404f66131bc9c22e06f712717288826487, c7fdb2404f66131bc9c22e06f712717288826487, c7fdb2404f66131bc9c22e06f712717288826487, c7fdb2404f66131bc9c22e06f712717288826487unaffected
LinuxLinux5.17, 0, 6.1.39, 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.