public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Edward Adam Davis <eadavis@qq.com>,
	syzbot+01cf2dbcbe2022454388@syzkaller.appspotmail.com,
	Dave Kleikamp <dave.kleikamp@oracle.com>,
	Sasha Levin <sashal@kernel.org>,
	shaggy@kernel.org, brauner@kernel.org, jack@suse.cz,
	jfs-discussion@lists.sourceforge.net
Subject: [PATCH AUTOSEL 6.6 05/19] jfs: fix uaf in jfs_evict_inode
Date: Mon, 15 Jan 2024 19:23:40 -0500	[thread overview]
Message-ID: <20240116002413.215163-5-sashal@kernel.org> (raw)
In-Reply-To: <20240116002413.215163-1-sashal@kernel.org>

From: Edward Adam Davis <eadavis@qq.com>

[ Upstream commit e0e1958f4c365e380b17ccb35617345b31ef7bf3 ]

When the execution of diMount(ipimap) fails, the object ipimap that has been
released may be accessed in diFreeSpecial(). Asynchronous ipimap release occurs
when rcu_core() calls jfs_free_node().

Therefore, when diMount(ipimap) fails, sbi->ipimap should not be initialized as
ipimap.

Reported-and-tested-by: syzbot+01cf2dbcbe2022454388@syzkaller.appspotmail.com
Signed-off-by: Edward Adam Davis <eadavis@qq.com>
Signed-off-by: Dave Kleikamp <dave.kleikamp@oracle.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
 fs/jfs/jfs_mount.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/fs/jfs/jfs_mount.c b/fs/jfs/jfs_mount.c
index b83aae56a1f2..631b8bd3e438 100644
--- a/fs/jfs/jfs_mount.c
+++ b/fs/jfs/jfs_mount.c
@@ -172,15 +172,15 @@ int jfs_mount(struct super_block *sb)
 	}
 	jfs_info("jfs_mount: ipimap:0x%p", ipimap);
 
-	/* map further access of per fileset inodes by the fileset inode */
-	sbi->ipimap = ipimap;
-
 	/* initialize fileset inode allocation map */
 	if ((rc = diMount(ipimap))) {
 		jfs_err("jfs_mount: diMount failed w/rc = %d", rc);
 		goto err_ipimap;
 	}
 
+	/* map further access of per fileset inodes by the fileset inode */
+	sbi->ipimap = ipimap;
+
 	return rc;
 
 	/*
-- 
2.43.0


  parent reply	other threads:[~2024-01-16  0:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16  0:23 [PATCH AUTOSEL 6.6 01/19] FS:JFS:UBSAN:array-index-out-of-bounds in dbAdjTree Sasha Levin
2024-01-16  0:23 ` [PATCH AUTOSEL 6.6 02/19] UBSAN: array-index-out-of-bounds in dtSplitRoot Sasha Levin
2024-01-16  0:23 ` [PATCH AUTOSEL 6.6 03/19] jfs: fix slab-out-of-bounds Read in dtSearch Sasha Levin
2024-01-16  0:23 ` [PATCH AUTOSEL 6.6 04/19] jfs: fix array-index-out-of-bounds in dbAdjTree Sasha Levin
2024-01-16  0:23 ` Sasha Levin [this message]
2024-01-16  0:23 ` [PATCH AUTOSEL 6.6 06/19] jfs: fix shift-out-of-bounds in dbJoin Sasha Levin
2024-01-16  0:23 ` [PATCH AUTOSEL 6.6 07/19] hwrng: starfive - Fix dev_err_probe return error Sasha Levin
2024-01-16  0:23 ` [PATCH AUTOSEL 6.6 08/19] crypto: p10-aes-gcm - Avoid -Wstringop-overflow warnings Sasha Levin
2024-01-16  0:23 ` [PATCH AUTOSEL 6.6 09/19] pstore/ram: Fix crash when setting number of cpus to an odd number Sasha Levin
2024-01-16  0:23 ` [PATCH AUTOSEL 6.6 10/19] erofs: fix up compacted indexes for block size < 4096 Sasha Levin
2024-01-16  0:23 ` [PATCH AUTOSEL 6.6 11/19] crypto: starfive - Fix dev_err_probe return error Sasha Levin
2024-01-16  0:23 ` [PATCH AUTOSEL 6.6 12/19] crypto: octeontx2 - Fix cptvf driver cleanup Sasha Levin
2024-01-16  0:23 ` [PATCH AUTOSEL 6.6 13/19] erofs: fix ztailpacking for subpage compressed blocks Sasha Levin
2024-01-16  0:23 ` [PATCH AUTOSEL 6.6 14/19] crypto: stm32/crc32 - fix parsing list of devices Sasha Levin
2024-01-16  0:23 ` [PATCH AUTOSEL 6.6 15/19] afs: fix the usage of read_seqbegin_or_lock() in afs_lookup_volume_rcu() Sasha Levin
2024-01-16  0:23 ` [PATCH AUTOSEL 6.6 16/19] afs: fix the usage of read_seqbegin_or_lock() in afs_find_server*() Sasha Levin
2024-01-16  0:23 ` [PATCH AUTOSEL 6.6 17/19] rxrpc_find_service_conn_rcu: fix the usage of read_seqbegin_or_lock() Sasha Levin
2024-01-16  0:23 ` [PATCH AUTOSEL 6.6 18/19] gfs2: Refcounting fix in gfs2_thaw_super Sasha Levin
2024-01-16  0:23 ` [PATCH AUTOSEL 6.6 19/19] jfs: fix array-index-out-of-bounds in diNewExt Sasha Levin

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=20240116002413.215163-5-sashal@kernel.org \
    --to=sashal@kernel.org \
    --cc=brauner@kernel.org \
    --cc=dave.kleikamp@oracle.com \
    --cc=eadavis@qq.com \
    --cc=jack@suse.cz \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaggy@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=syzbot+01cf2dbcbe2022454388@syzkaller.appspotmail.com \
    /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