In the Linux kernel, the following vulnerability has been resolved:
i2c: cadence: cdns_i2c_master_xfer(): Fix runtime PM leak on error path
The cdns_i2c_master_xfer() function gets a runtime PM reference when the
function is entered. This reference is released when the function is
exited. There is currently one error path where the function exits
directly, which leads to a leak of the runtime PM reference.
Make sure that this error path also releases the runtime PM reference.
Security readout for executives and security teams
Plain-English summary
CVE-2023-54009 is a Linux kernel defect in the Cadence I2C driver. On one transfer error path, the driver fails to release a runtime power-management reference. This is a resource-management bug, not a disclosed remote code execution issue.
Executive priority
Treat this as a targeted kernel maintenance item unless your environment relies on Cadence I2C hardware. There is no source-backed evidence of active exploitation, but affected embedded or appliance platforms should receive vendor kernel updates through normal patch governance.
Technical view
The issue is in cdns_i2c_master_xfer(). The function acquires a runtime PM reference on entry and normally releases it on exit. One direct error return skipped that release, causing a runtime PM reference leak. Kernel stable commits correct the error path to release the reference.
Likely exposure
Exposure is most likely on Linux systems using the Cadence I2C controller driver, commonly relevant to embedded or SoC-based hardware. The source bundle does not provide CVSS, CWE, CPEs, or a precise product matrix beyond Linux kernel version data and stable fix references.
Exploitation context
The bundle does not indicate active exploitation, public exploit availability, or KEV listing. The described impact is a driver runtime power-management reference leak triggered on an error path, but the sources do not document attacker prerequisites or practical exploitability.
Researcher notes
The main uncertainty is impact characterization. The CVE text documents a concrete bug and fix but omits CVSS, CWE, exploitability, and detailed affected-version semantics. Analysis should focus on driver reachability, hardware presence, and whether downstream kernels backported the stable patches.
Mitigation direction
Update to a kernel containing the referenced stable fixes.
Check distribution or device-vendor advisories for patched kernel packages.
Prioritize systems using Cadence I2C hardware or driver support.
If patching is delayed, assess whether the driver is present and active.
Validation and detection
Confirm the running kernel includes one referenced stable commit or downstream backport.
Review vendor kernel changelogs for CVE-2023-54009 or the fix title.
Inventory systems with Cadence I2C controller support enabled.
Confirm no unsupported custom kernel is missing the runtime PM fix.
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-54009 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
7Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 24, 2025, 10:55 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.