CVE-2024-46728

What it actually does

Unchecked array index into a 7-element aux_rd_interval buffer allows out-of-bounds read/write and integer overflow in the AMD display driver code path.

Why it matters to the business

Local users on affected Linux kernels with AMD GPUs can trigger kernel memory corruption leading to crashes, denial of service, or potential privilege escalation on graphics-enabled systems.

How an attack unfolds

An attacker with local access crafts a display configuration or triggers the aux channel read interval path that supplies an index outside the valid 0-6 range; the missing bounds check causes the kernel to access invalid memory, resulting in the reported overrun or overflow conditions.

How to fix it

Apply the upstream fix by updating the Linux kernel to a version containing commit 48e0b68e2360b16edf2a0bae05c0051c00fbb48a or later; rebuild and reboot with the patched kernel.

How to confirm the fix worked

Confirm the presence of the index check on aux_rd_interval in the drm/amd/display source and verify the running kernel reports the patched commit or a version after 2024-09-18.

Typical attack path

1. Obtain local unprivileged shell on target Linux system with AMD display hardware
2. Trigger DRM/AMD display aux_rd_interval code path via userspace display or mode-setting APIs
3. Supply index value >=7 to bypass the absent bounds check
4. Cause kernel memory corruption or integer overflow to achieve denial of service or escalate privileges

How to detect it

Review kernel logs for display driver oops or panic messages referencing aux_rd_interval or drm/amd/display; inspect audit logs for unusual display configuration changes by non-root users.

What your security team should do

• Immediately schedule kernel updates containing the referenced commit for all AMD GPU systems
• Restrict unprivileged local access on multi-user systems until patches are deployed
• Monitor for kernel oops or display driver crashes as indicators of attempted exploitation