CVE-2024-35943

What it actually does

Missing null pointer check after devm_kasprintf() in omap_prm_domain_init allows a failed memory allocation to be dereferenced, resulting in a kernel NULL pointer dereference.

Why it matters to the business

Kernel crashes or system instability on affected Linux distributions can interrupt services and require reboots or rollbacks.

How an attack unfolds

An attacker would need to trigger the power domain initialization path under memory pressure so that devm_kasprintf returns NULL, causing an immediate dereference when the pointer is used; no public exploits or threat actor campaigns have been observed.

How to fix it

Apply the upstream fix in commit e65f7eb117e1b44742212d65784236269085e736 or later; rebuild and deploy updated kernel packages for all affected stable trees.

How to confirm the fix worked

Confirm the presence of the null check after devm_kasprintf in omap_prm_domain_init in the running kernel source or verify the commit is included in the deployed kernel version.

Typical attack path

1. Gain local access or control a workload that can influence kernel memory allocation
2. Force the omap_prm_domain_init path to execute while allocations are failing
3. Trigger NULL dereference and resulting kernel panic or oops

How to detect it

Review kernel logs for oops or panic messages containing omap_prm_domain_init or devm_kasprintf; no specific post-exploitation artifacts are known.

What your security team should do

• Prioritize kernel updates containing commit e65f7eb117e1b44742212d65784236269085e736 on all systems
• Monitor for kernel oops or panic reports referencing pmdomain/ti code paths
• Apply updates within normal patch windows given low EPSS and absence from KEV