Kernel memory exhaustion via unreleased ATOM BIOS allocation
Published Oct 1, 2025 · Updated Oct 1, 2025
Memory leak in the radeon ATOM BIOS teardown in affected Linux kernels allows local users to exhaust kernel memory during driver unload. The atom_index_iio() path allocates iio during atom_parse(), but radeon_atombios_fini() fails to release that allocation when the driver shuts down. Triggering the leak requires local access able to unload the radeon driver; repeated unload cycles consume kernel memory and can interrupt service.
Summary
What happened
Memory leak in the radeon ATOM BIOS teardown in affected Linux kernels allows local users to exhaust kernel memory during driver unload. The atom_index_iio() path allocates iio during atom_parse(), but radeon_atombios_fini() fails to release that allocation when the driver shuts down. Triggering the leak requires local access able to unload the radeon driver; repeated unload cycles consume kernel memory and can interrupt service.
The record
- CVE
- CVE-2023-53453
- Published
- Oct 1, 2025
- Updated
- Oct 1, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 1, 2025CVE publishedPublication date reported by the CVE source.
- Oct 1, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <107b8b542bb9dab4cbdc3276c85fbdd7f6782313
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4773fadedca918faec443daaca5e4ea1c0ced144
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9cdb96b55651c92fc949cfd54124406c3c912b6b
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cb109cedbba11c33473e6780c256d8442a9e4460
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <cda2f7efbc2d857220dad32e315a54565b285c1c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ce9e9d3dcbb0d1551ffd1a7f16e7c051f3ba4140
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e2791f2f4d1d804e45fa91b14295c326b64c65f1
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f9f55fc64928b5e30d78f861c5fc76db9e769ebb
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo