lib: cpu_rmap: Avoid use after free on rmap->obj array entries
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 896f97ea95c1d29c0520ee0766b66b7f64cb967c · < c9115f49cf260d24d8b5f2d9a4b63cb31a627bb4| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
lib: cpu_rmap: Avoid use after free on rmap->obj array entries
When calling irq_set_affinity_notifier() with NULL at the notify argument, it will cause freeing of the glue pointer in the corresponding array entry but will leave the pointer in the array. A subsequent call to free_irq_cpu_rmap() will try to free this entry again leading to possible use after free.
Fix that by setting NULL to the array entry and checking that we have non-zero at the array entry when iterating over the array in free_irq_cpu_rmap().
The current code does not suffer from this since there are no cases where irq_set_affinity_notifier(irq, NULL) (note the NULL passed for the notify arg) is called, followed by a call to free_irq_cpu_rmap() so we don't hit and issue. Subsequent patches in this series excersize this flow, hence the required fix.
From the CVE record · Linux
The Linux kernel’s cpu_rmap code can leave a freed pointer in an array when irq_set_affinity_notifier() is called with a NULL notifier. A later call to free_irq_cpu_rmap() could use that pointer, but the described current code does not exercise this call sequence; the input does not specify attacker access or user-interaction requirements.
Engineers running the Linux kernel should check whether their kernel includes the affected cpu_rmap code; affected versions are not specified.