CVE-2026-72485
HighCVSS 7.8Exploitation Probability (EPSS)
Low risk5th percentile - higher than 5% of all known CVEs
Summary
In the Linux kernel, the coresight platform subsystem has an issue where connection counters are incremented before successful memory allocation. If allocation fails, the counter remains incremented, and cleanup functions may dereference invalid pointers, causing a kernel panic. The fix moves counter increments after all allocations succeed.
Risk Assessment
During failed initialization of a coresight device, a kernel panic may occur, leading to system unavailability. An attacker with local access could deliberately trigger this scenario.
Recommendation
Install the patch from the Linux kernel that moves counter increments after allocations. Update the kernel to a patched version.
Original NVD description (English source)
In the Linux kernel, the following vulnerability has been resolved: coresight: platform: defer connection counter increment until alloc succeeds coresight_add_out_conn() increments nr_outconns before calling devm_krealloc_array() and again before devm_kmalloc(). If either allocation fails, the counter is already bumped while the corresponding array entry is NULL or uninitialized garbage. coresight_add_in_conn() has the same problem with nr_inconns and devm_krealloc_array(). In both cases the probe returns -ENOMEM, which causes coresight_get_platform_data() to call coresight_release_platform_data() for cleanup. That function iterates up to nr_outconns (or nr_inconns) entries and dereferences each pointer unconditionally, hitting the NULL or garbage entry and panicking instead of failing gracefully. Fix by moving the counter increments to after all allocations succeed, so the struct is always consistent on any error path.