CVE-2021-47445

What it actually does

The code dereferences pointer 'edp' to initialize 'dev' before performing a null check on 'edp', creating a potential null pointer dereference condition.

Why it matters to the business

Systems may experience unexpected crashes or instability when the vulnerable code path is exercised, potentially disrupting operations until patched.

How an attack unfolds

An attacker supplies conditions that leave the 'edp' pointer null when the initialization code runs, triggering the dereference before the safety check and causing a crash or undefined behavior.

How to fix it

Update to a fixed version such as commit 129700d74d83f9b9a82bf88ebc63707e3cb0a725 in the affected package.

How to confirm the fix worked

Confirm the source contains the null check on edp prior to any dereference for initializing dependent pointers; review commit history for the referenced fix.

Typical attack path

1. Identify a system running an unpatched version of the affected component
2. Trigger the code path that initializes the dev pointer from edp
3. Ensure edp remains null at the point of dereference
4. Observe kernel panic or application fault

How to detect it

Review kernel logs for null pointer dereference oops messages referencing drm/msm or edp initialization; examine recent changes to display driver code.

What your security team should do

• Apply the listed fixed commit immediately given the memory corruption family
• Scan for any downstream dependents that may inherit the vulnerable code
• Monitor for stability issues in graphics or display subsystems until updated