CVE-2023-53682: hwmon: (xgene) Fix ioremap and memremap leak
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (xgene) Fix ioremap and memremap leak
Smatch reports:
drivers/hwmon/xgene-hwmon.c:757 xgene_hwmon_probe() warn:
'ctx->pcc_comm_addr' from ioremap() not released on line: 757.
This is because in drivers/hwmon/xgene-hwmon.c:701 xgene_hwmon_probe(),
ioremap and memremap is not released, which may cause a leak.
To fix this, ioremap and memremap is modified to devm_ioremap and
devm_memremap.
[groeck: Fixed formatting and subject]
Security readout for executives and security teams
Plain-English summary
CVE-2023-53682 is a Linux kernel issue in the xgene hardware monitoring driver. The driver could leak mapped memory resources during device probing. Public sources do not provide a CVSS score, impact assessment, or evidence of active exploitation. Business urgency is mainly for organizations running affected Linux kernels on systems that use this driver.
Executive priority
Treat as a targeted kernel maintenance item, not an emergency, unless your environment uses affected xgene hardware monitoring paths. Include it in routine kernel patch cycles and confirm vendor applicability because public severity and exploit evidence are limited.
Technical view
The issue is in drivers/hwmon/xgene-hwmon.c xgene_hwmon_probe(). ioremap() and memremap() resources were not released on an error path, causing a leak. The kernel fix changes these to devm_ioremap() and devm_memremap() so cleanup is device-managed. References point to Linux stable commits addressing the flaw.
Likely exposure
Exposure appears limited to Linux systems with affected kernel versions and the xgene hwmon driver path in use. The CVE data lists Linux kernel versions including 4.9, 6.1.25, 6.2.12, and 6.3 as affected, but the provided data does not give complete version range semantics.
Exploitation context
No CISA KEV listing is indicated, and the provided sources do not report active exploitation. The described bug is a resource leak in kernel driver initialization, not a clearly documented remote code execution or privilege escalation path in the available sources.
Researcher notes
The public record frames this as a resolved Linux kernel resource leak found by Smatch. Severity, CWE, and CVSS are not provided. Affected-version data is sparse and should be validated against distribution backports and the three upstream stable commits before making exposure claims.
Mitigation direction
Review Linux vendor advisories for CVE-2023-53682 applicability to your kernel builds.
Update to a kernel containing the referenced stable fixes where applicable.
Prioritize systems using the xgene hardware monitoring driver.
If vendor packages are unavailable, track the listed upstream stable commits.
Validation and detection
Inventory Linux kernel versions across servers and appliances.
Check whether the xgene hwmon driver is built, loaded, or relevant to the hardware.
Compare deployed kernels against vendor advisories and referenced stable commits.
Monitor kernel logs for hardware monitoring probe errors on relevant systems.
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-53682 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
4Source 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.
Oct 7, 2025, 15:21 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.