From: email@example.com To: firstname.lastname@example.org Subject: [Bug 208751] KASAN: Use-after-free bug in xlog_alloc_log Date: Fri, 31 Jul 2020 19:20:51 +0000 Message-ID: <bug-208751-201763-d8YDcQKuP2@https.bugzilla.kernel.org/> (raw) In-Reply-To: <email@example.com/> https://bugzilla.kernel.org/show_bug.cgi?id=208751 Eric Sandeen (firstname.lastname@example.org) changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |email@example.com Resolution|--- |PATCH_ALREADY_AVAILABLE --- Comment #1 from Eric Sandeen (firstname.lastname@example.org) --- You've reported this on a 5.4.0 kernel from November 2019 (please, in future bug reports include the kernel version more prominently) This commit: commit 798a9cada4694ca8d970259f216cec47e675bfd5 Author: Brian Foster <email@example.com> Date: Tue Dec 3 07:53:15 2019 -0800 xfs: fix mount failure crash on invalid iclog memory access syzbot (via KASAN) reports a use-after-free in the error path of xlog_alloc_log(). Specifically, the iclog freeing loop doesn't handle the case of a fully initialized ->l_iclog linked list. Instead, it assumes that the list is partially constructed and NULL terminated. This bug manifested because there was no possible error scenario after iclog list setup when the original code was added. Subsequent code and associated error conditions were added some time later, while the original error handling code was never updated. Fix up the error loop to terminate either on a NULL iclog or reaching the end of the list. Reported-by: firstname.lastname@example.org Signed-off-by: Brian Foster <email@example.com> Reviewed-by: Darrick J. Wong <firstname.lastname@example.org> Signed-off-by: Darrick J. Wong <email@example.com> went into v5.5 I believe this is already resolved; if you have a reproducer can you please test? If you believe this bug is still not fixed, please re-open this bug. -- You are receiving this mail because: You are watching the assignee of the bug.
parent reply index Thread overview: expand[flat|nested] mbox.gz Atom feed [parent not found: <firstname.lastname@example.org/>]
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=bug-208751-201763-d8YDcQKuP2@https.bugzilla.kernel.org/ \ --email@example.com \ --firstname.lastname@example.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
Linux-XFS Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-xfs/0 linux-xfs/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-xfs linux-xfs/ https://lore.kernel.org/linux-xfs \ email@example.com public-inbox-index linux-xfs Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-xfs AGPL code for this site: git clone https://public-inbox.org/public-inbox.git