LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54230: amba: bus: fix refcount leak

In the Linux kernel, the following vulnerability has been resolved: amba: bus: fix refcount leak commit 5de1540b7bc4 ("drivers/amba: create devices from device tree") increases the refcount of of_node, but not releases it in amba_device_release, so there is refcount leak. By using of_node_put to avoid refcount leak.

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-54230 is a Linux kernel bug where AMBA bus device handling leaks a device-tree reference count. In practical terms, it is a kernel resource-management flaw, not a confirmed remote compromise issue. Business urgency is lower unless you operate affected Linux kernels on systems using this AMBA/device-tree path and require high uptime.

Executive priority

Treat as routine kernel maintenance unless affected platforms are business-critical or uptime-sensitive. There is no sourced evidence of active exploitation, but kernel resource leaks should still be remediated through normal patch cycles.

Technical view

The Linux kernel AMBA bus code increments an of_node reference when creating devices from device tree but failed to release it in amba_device_release. The fix adds of_node_put to avoid the refcount leak. The CVE lists multiple affected stable kernel lines and references stable backport commits.

Likely exposure

Exposure is most likely on Linux systems running the listed affected kernel versions where AMBA bus devices are created from device tree. This commonly matters for kernel builds and platforms using that driver path. The CVE data does not identify specific distributions, appliances, or cloud services.

Exploitation context

No active exploitation is indicated in the provided sources, and the CVE is not marked KEV. The available description points to a reference-count leak, which may affect reliability or resource handling. The sources do not describe privilege escalation, remote attack, or public exploit behavior.

Researcher notes

The record lacks CVSS, CWE, and detailed impact analysis. Affected version data is broad and commit-oriented. Validate exposure by kernel branch and configuration, not CVE presence alone. Avoid assuming exploitability beyond the documented refcount leak.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable fix for your kernel branch.
  • Check your Linux distribution or device vendor advisory for packaged kernel updates.
  • Prioritize systems using AMBA bus/device-tree configurations if maintenance windows are constrained.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Compare running kernels against vendor-fixed releases or the referenced stable commits.
  • Confirm whether deployed platforms use AMBA bus devices from device tree.
  • Track reboot completion after kernel update where required.
Prepared
Confidence
medium
Sources
11

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-54230 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
10Source 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
LinuxLinux5de1540b7bc4c23470f86add1e517be41e7fefe2, 5de1540b7bc4c23470f86add1e517be41e7fefe2, 5de1540b7bc4c23470f86add1e517be41e7fefe2, 5de1540b7bc4c23470f86add1e517be41e7fefe2, 5de1540b7bc4c23470f86add1e517be41e7fefe2, 5de1540b7bc4c23470f86add1e517be41e7fefe2, 5de1540b7bc4c23470f86add1e517be41e7fefe2, 5de1540b7bc4c23470f86add1e517be41e7fefe2, 5de1540b7bc4c23470f86add1e517be41e7fefe2unaffected
LinuxLinux3.1, 0, 4.14.326, 4.19.295, 5.4.257, 5.10.195, 5.15.132, 6.1.53, 6.4.16, 6.5.3, 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.