LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53453: drm/radeon: free iio for atombios when driver shutdown

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: [<0000000062fadebe>] kmem_cache_alloc_trace+0x2f1/0x500 [<00000000b6883cea>] atom_parse+0x117/0x230 [radeon] [<00000000158c23fd>] radeon_atombios_init+0xab/0x170 [radeon] [<00000000683f672e>] si_init+0x57/0x750 [radeon] [<00000000566cc31f>] radeon_device_init+0x559/0x9c0 [radeon] [<0000000046efabb3>] radeon_driver_load_kms+0xc1/0x1a0 [radeon] [<00000000b5155064>] drm_dev_register+0xdd/0x1d0 [<0000000045fec835>] radeon_pci_probe+0xbd/0x100 [radeon] [<00000000e69ecca3>] pci_device_probe+0xe1/0x160 [<0000000019484b76>] really_probe.part.0+0xc1/0x2c0 [<000000003f2649da>] __driver_probe_device+0x96/0x130 [<00000000231c5bb1>] driver_probe_device+0x24/0xf0 [<0000000000a42377>] __driver_attach+0x77/0x190 [<00000000d7574da6>] bus_for_each_dev+0x7f/0xd0 [<00000000633166d2>] driver_attach+0x1e/0x30 [<00000000313b05b8>] 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().

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2023-53453 is a Linux kernel radeon graphics driver memory leak. When the radeon driver shuts down or unloads, memory allocated during ATOM BIOS parsing was not released. The provided sources do not show active exploitation, a CVSS score, or direct data compromise impact.

Executive priority

Treat as routine kernel hygiene unless your fleet heavily uses legacy Radeon hardware or frequently reloads graphics drivers. There is no provided evidence of active exploitation or data compromise, but kernel updates should still be folded into normal maintenance.

Technical view

The flaw is in drm/radeon ATOM BIOS handling. atom_parse allocates iio through atom_index_iio, but radeon_atombios_fini did not free it during driver shutdown. Kernel stable commits address this by freeing the allocation. Evidence points to a kmemleak on driver unload, not a documented privilege escalation path.

Likely exposure

Exposure is most likely on Linux systems using the radeon DRM driver with affected kernel versions and Radeon hardware. Systems not loading radeon, using unaffected fixed kernels, or using different graphics drivers are less likely to be exposed.

Exploitation context

The source bundle states KEV is false and provides no public exploitation evidence. The described trigger is driver shutdown or unload causing unreleased kernel memory. No exploit steps, weaponized technique, or attacker-controlled path is documented in the provided sources.

Researcher notes

The record lacks CVSS, CWE, and exploitability detail. The evidence is a Linux stable fix for a leaked 512-byte allocation tied to radeon ATOM BIOS parsing. Analysis should stay limited to resource leakage unless additional vendor or kernel discussion documents security impact.

Mitigation direction

  • Identify systems loading the Linux radeon kernel module.
  • Apply the relevant Linux stable kernel update containing the listed fix commits.
  • Prioritize hosts where radeon unloads, reloads, or GPU drivers are operationally cycled.
  • Check distribution vendor advisories for packaged kernel availability and backports.
  • Avoid manual driver cycling as a mitigation substitute.

Validation and detection

  • Confirm running kernel version against vendor-fixed packages or listed stable commits.
  • Check whether the radeon module is loaded on candidate systems.
  • Review kernel logs or kmemleak findings for radeon ATOM BIOS leaks.
  • Validate patched systems no longer report this leak after controlled driver shutdown testing.
Prepared
Confidence
medium
Sources
10

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-53453 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
9Source 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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux771fe6b912fca54f03e8a72eb63058b582775362, 771fe6b912fca54f03e8a72eb63058b582775362, 771fe6b912fca54f03e8a72eb63058b582775362, 771fe6b912fca54f03e8a72eb63058b582775362, 771fe6b912fca54f03e8a72eb63058b582775362, 771fe6b912fca54f03e8a72eb63058b582775362, 771fe6b912fca54f03e8a72eb63058b582775362, 771fe6b912fca54f03e8a72eb63058b582775362unaffected
LinuxLinux2.6.31, 0, 4.14.308, 4.19.276, 5.4.235, 5.10.173, 5.15.99, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.