summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorEli Cohen <elic@nvidia.com>2023-02-08 07:51:02 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2023-05-30 12:38:35 +0100
commit981f339d2905b6a92ef59358158b326493aecac5 (patch)
tree8ae177c0e1f5466b894fd78eded79465d09b1b13 /drivers
parent2b8687adc874d7ce409ea32b35b39578db64086d (diff)
downloadlinux-stable-981f339d2905b6a92ef59358158b326493aecac5.tar.gz
linux-stable-981f339d2905b6a92ef59358158b326493aecac5.tar.bz2
linux-stable-981f339d2905b6a92ef59358158b326493aecac5.zip
lib: cpu_rmap: Avoid use after free on rmap->obj array entries
[ Upstream commit 4e0473f1060aa49621d40a113afde24818101d37 ] 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 <tglx@linutronix.de> Signed-off-by: Eli Cohen <elic@nvidia.com> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com> Reviewed-by: Jacob Keller <jacob.e.keller@intel.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions