diff options
author | Eli Cohen <[email protected]> | 2023-02-08 07:51:02 +0200 |
---|---|---|
committer | Saeed Mahameed <[email protected]> | 2023-03-24 16:03:52 -0700 |
commit | 4e0473f1060aa49621d40a113afde24818101d37 (patch) | |
tree | 2db1638290f344047b2651332f4919ede909513a /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | e8d018dd0257f744ca50a729e3d042cf2ec9da65 (diff) |
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.
Cc: Thomas Gleixner <[email protected]>
Signed-off-by: Eli Cohen <[email protected]>
Signed-off-by: Saeed Mahameed <[email protected]>
Reviewed-by: Jacob Keller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions