CVE-2024-46816

What it actually does

The flaw permits an array overrun of dc->links when link count exceeds max_links during AMD display initialization in the Linux kernel, as no bounds check existed before the Coverity-reported condition.

Why it matters to the business

Systems using AMD GPUs may experience crashes or instability during display initialization with many connected outputs, disrupting operations; low urgency given absence from KEV and stable low EPSS.

How an attack unfolds

An attacker supplies or triggers a display configuration that sets link count above the maximum during amdgpu_dm initialization, leading to out-of-bounds access; listed threat actors reference generic Linux kernel and Android kernel campaigns but no confirmed exploitation of this specific issue.

How to fix it

Update the Linux kernel to commit e2411b6abf6e5d6c33d0450846673cdf536f0ba4 or equivalent fixed version that adds the link count check before initialization.

How to confirm the fix worked

Verify kernel source contains the bounds check on link count versus max_links; test initialization with high display counts post-update to confirm no overrun warning or crash.

Typical attack path

1. Gain local access or load kernel modules on a vulnerable AMD-based Linux system
2. Configure or emulate more display links than max_links (up to 31)
3. Trigger AMD display driver initialization path
4. Cause array overrun during dc->links population

How to detect it

Review kernel logs and dmesg for AMD display initialization failures or array access warnings; correlate with systems reporting high display link counts during boot or hotplug events.

What your security team should do

• Apply the referenced kernel commit or stable update containing the fix
• Limit display configurations to known safe link counts where possible
• Monitor kernel logs for AMD display initialization errors