stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amy Fong <Amy_Fong@mentor.com>
To: <stable@vger.kernel.org>
Cc: <Amy_Fong@mentor.com>, <davem@davemloft.net>
Subject: [PATCH 4.19 stable 0/5] Backport netfilter: nf_tables: autoload modules from the abort path
Date: Tue, 11 Jan 2022 10:37:13 -0500	[thread overview]
Message-ID: <Yd2kKZEWm6AdBYDE@cat> (raw)

The following series backports netfilter: nf_tables: autoload modules from abort path
which fixes the bug mentioned in the following:

   https://syzkaller.appspot.com/bug?extid=437bf61d165c87bd40fb


----

BUG: corrupted list in __nf_tables_abort
Status: fixed on 2020/03/17 22:09
Reported-by: syzbot+437bf61d165c87bd40fb@syzkaller.appspotmail.com
Fix commit: eb014de4fd41 netfilter: nf_tables: autoload modules from the abort path
First crash: 717d, last: 710d

Cause bisection: introduced by (bisect log) :
commit ec7470b834fe7b5d7eff11b6677f5d7fdf5e9a91
Author: Pablo Neira Ayuso <pablo@netfilter.org>
Date: Mon Jan 13 17:09:58 2020 +0000

  netfilter: nf_tables: store transaction list locally while requesting module

Crash: KASAN: use-after-free Read in __nf_tables_abort (log)
Repro: C syz .config

Fix bisection: fixed by (bisect log) :
commit 34682110abc50ffea7e002b0c2fd7ea9e0000ccc
Author: Max Chou <max.chou@realtek.com>
Date: Wed Nov 27 03:01:07 2019 +0000

  Bluetooth: btusb: Edit the logical value for Realtek Bluetooth reset
'

             reply	other threads:[~2022-01-11 15:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 15:37 Amy Fong [this message]
2022-01-11 15:40 ` [PATCH 4.19 stable 1/5] Backport netfilter: nf_tables: autoload modules from the abort path Amy Fong
2022-01-11 15:40 ` [PATCH 4.19 stable 2/5] " Amy Fong
2022-01-11 15:41 ` [PATCH 4.19 stable 3/5] " Amy Fong
2022-01-11 15:41 ` [PATCH 4.19 stable 4/5] " Amy Fong
2022-01-11 15:42 ` [PATCH 4.19 stable 5/5] " Amy Fong
2022-01-11 17:50 ` [PATCH 4.19 stable 0/5] " Greg KH
2022-01-11 17:52 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yd2kKZEWm6AdBYDE@cat \
    --to=amy_fong@mentor.com \
    --cc=davem@davemloft.net \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).