CVE-2023-53453

EPSS 0.0%
  • Published: 2025-10-01T12:15:43.787

In the Linux kernel, the following vulnerability has been resolved:

drm/radeon: free iio for atombios when driver shutdown

Fix below kmemleak when unload radeon driver:

unreferenced object 0xffff9f8608ede200 (size 512):
comm “systemd-udevd”, pid 326, jiffies 4294682822 (age 716.338s)
hex dump (first 32 bytes):
00 00 00 00 c4 aa ec aa 14 ab 00 00 00 00 00 00 …………….
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 …………….
backtrace:
[] kmem_cache_alloc_trace+0x2f1/0x500
[] atom_parse+0x117/0x230 [radeon]
[] radeon_atombios_init+0xab/0x170 [radeon]
[] si_init+0x57/0x750 [radeon]
[] radeon_device_init+0x559/0x9c0 [radeon]
[] radeon_driver_load_kms+0xc1/0x1a0 [radeon]
[] drm_dev_register+0xdd/0x1d0
[] radeon_pci_probe+0xbd/0x100 [radeon]
[] pci_device_probe+0xe1/0x160
[] really_probe.part.0+0xc1/0x2c0
[] __driver_probe_device+0x96/0x130
[] driver_probe_device+0x24/0xf0
[] __driver_attach+0x77/0x190
[] bus_for_each_dev+0x7f/0xd0
[] driver_attach+0x1e/0x30
[] bus_add_driver+0x12c/0x1e0

iio was allocated in atom_index_iio() called by atom_parse(),
but it doesn’t got released when the dirver is shutdown.
Fix this kmemleak by free it in radeon_atombios_fini().

Related CVE by CWE

No related CWE found.

Top CVE for Vendor

No vendor taxonomy on this entry.

Recently Exploited Similar Vulnerabilities

No recent KEV-listed items for this vendor/product.

How to fix CVE-2023-53453

CVE-2023-53453 is a unknown severity vulnerability affecting the affected product.

Description: In the Linux kernel, the following vulnerability has been resolved: drm/radeon: free iio for atombios when driver shutdown Fix below kmemleak when unload radeon driver: unreferenced object 0xffff9f8608ede200 (size 512): comm “systemd-udevd”, pid 326, jiffies 4294682822 (age 716.338s) hex dump (first 32 bytes): 00 00 00 00 c4 aa ec aa 14 ab 00 00 […]

Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public

How to Fix:

1 Identify affected systems

- Check if you're running the affected product

2 Immediate actions

- Update to the latest patched version
- If patching is not immediately possible: restrict network exposure, apply least-privilege access

3 Verification

- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)

4 Long-term prevention

- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations

Exploit Difficulty Assessment

HARD
⏱️ Time to Exploit: > 4 hours
🛠️ Skills Required: Advanced security expertise
💰 Public Exploits: Rare or not public

Vulnerability Timeline

Oct 01, 2025
Vulnerability Published

CVE details first published to NVD database

Nov 12, 2025
Imported to Database

Added to this CVE tracking system

Detection Rules & IOCs

No specific detection rules generated for this vulnerability type.

No vendor/product data available.