Linux vulnerability

What happened

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.

Affected versions

Linux: 3d4ff657e454f8dba3e5e268e731e6e28c6031c1 through before dd3c9e1c9858c797ba78f4ca6c0fc663eeac6d72 (git); 3d4ff657e454f8dba3e5e268e731e6e28c6031c1 through before aed6915c2f304ed34281856c53e374483c71b68b (git); 3d4ff657e454f8dba3e5e268e731e6e28c6031c1 through before 09c44549820df67048be3ba19c723bac72ebb98e (git); 3d4ff657e454f8dba3e5e268e731e6e28c6031c1 through before 8ca9adc805884d3bb5038082462577f86c2c4a10 (git); 3d4ff657e454f8dba3e5e268e731e6e28c6031c1 through before 1563ae33dc4f5ebac96b93af2ef72e72aaaa31ae (git); 6.5 Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

• Apply vendor-provided updates or mitigations.
• Review affected product exposure and access logs.