Skip to contentSkip to conversation

genirq: Prevent use-after-free and work list corruption]

PATCH In review Ingo Molnar 3 participants 4 messages May 7, 2019 – May 9, 2019

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 genirq: Prevent use-after-free and work list corruption]

Hi Greg,

We forgot to mark 59c39840f5abf4a71e1 for -stable, please apply. It should apply cleanly all the way back to v3.0.

Thanks,

Ingo

----- Forwarded message from tip-bot for Prasad Sodagudi <[email protected]> -----

Date: Sun, 24 Mar 2019 14:16:45 -0700
From: tip-bot for Prasad Sodagudi <[email protected]>
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: [tip:irq/core] genirq: Prevent use-after-free and work list corruption

Commit-ID:  59c39840f5abf4a71e1810a8da71aaccd6c17d26
Gitweb:     https://git.kernel.org/tip/59c39840f5abf4a71e1810a8da71aaccd6c17d26
Author:     Prasad Sodagudi <[email protected]>
AuthorDate: Sun, 24 Mar 2019 07:57:04 -0700
Committer:  Thomas Gleixner <[email protected]>
CommitDate: Sun, 24 Mar 2019 22:13:17 +0100

genirq: Prevent use-after-free and work list corruption

When irq_set_affinity_notifier() replaces the notifier, then the reference count on the old notifier is dropped which causes it to be freed. But nothing ensures that the old notifier is not longer queued in the work list. If it is queued this results in a use after free and possibly in work list corruption.

Ensure that the work is canceled before the reference is dropped.

---
 kernel/irq/manage.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)
kernel/irq/manage.c +3 -1
index 1401afa0d58a..53a081392115 100644
@@ -357,8 +357,10 @@ irq_set_affinity_notifier(unsigned int irq, struct irq_affinity_notify *notify)
 	desc->affinity_notify = notify;
 	raw_spin_unlock_irqrestore(&desc->lock, flags);
 
-	if (old_notify)
+	if (old_notify) {
+		cancel_work_sync(&old_notify->work);
 		kref_put(&old_notify->kref, old_notify->release);
+	}
 
 	return 0;
 }

----- End forwarded message -----

maintainer
#1 lore raw
Quoted 5 lines · Ingo Molnar

Hi Greg,

We forgot to mark 59c39840f5abf4a71e1 for -stable, please apply. It should apply cleanly all the way back to v3.0.

Thanks, will do for the next round of releases after this one.

greg k-h

maintainer
#2 lore raw
Quoted 8 lines · Greg KH
Quoted 5 lines · Ingo Molnar

Hi Greg,

We forgot to mark 59c39840f5abf4a71e1 for -stable, please apply. It should apply cleanly all the way back to v3.0.

Thanks, will do for the next round of releases after this one.

I've queued it for all branches.

--
Thanks,
Sasha

maintainer
#3 lore raw
Quoted 11 lines · Sasha Levin
Quoted 8 lines · Greg KH
Quoted 5 lines · Ingo Molnar

Hi Greg,

We forgot to mark 59c39840f5abf4a71e1 for -stable, please apply. It should apply cleanly all the way back to v3.0.

Thanks, will do for the next round of releases after this one.

I've queued it for all branches.

You forgot the 5.1.y branch :(

Now added there too, thanks.

greg k-h