Skip to content

Commit b15fa92

Browse files
vvidictorvalds
authored andcommitted
ocfs2: mount fails with buffer overflow in strlen
Starting with kernel 5.11 built with CONFIG_FORTIFY_SOURCE mouting an ocfs2 filesystem with either o2cb or pcmk cluster stack fails with the trace below. Problem seems to be that strings for cluster stack and cluster name are not guaranteed to be null terminated in the disk representation, while strlcpy assumes that the source string is always null terminated. This causes a read outside of the source string triggering the buffer overflow detection. detected buffer overflow in strlen ------------[ cut here ]------------ kernel BUG at lib/string.c:1149! invalid opcode: 0000 [#1] SMP PTI CPU: 1 PID: 910 Comm: mount.ocfs2 Not tainted 5.14.0-1-amd64 #1 Debian 5.14.6-2 RIP: 0010:fortify_panic+0xf/0x11 ... Call Trace: ocfs2_initialize_super.isra.0.cold+0xc/0x18 [ocfs2] ocfs2_fill_super+0x359/0x19b0 [ocfs2] mount_bdev+0x185/0x1b0 legacy_get_tree+0x27/0x40 vfs_get_tree+0x25/0xb0 path_mount+0x454/0xa20 __x64_sys_mount+0x103/0x140 do_syscall_64+0x3b/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae Link: https://lkml.kernel.org/r/[email protected] Signed-off-by: Valentin Vidic <[email protected]> Reviewed-by: Joseph Qi <[email protected]> Cc: Mark Fasheh <[email protected]> Cc: Joel Becker <[email protected]> Cc: Junxiao Bi <[email protected]> Cc: Changwei Ge <[email protected]> Cc: Gang He <[email protected]> Cc: Jun Piao <[email protected]> Cc: <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
1 parent 5314454 commit b15fa92

File tree

1 file changed

+10
-4
lines changed

1 file changed

+10
-4
lines changed

fs/ocfs2/super.c

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2167,11 +2167,17 @@ static int ocfs2_initialize_super(struct super_block *sb,
21672167
}
21682168

21692169
if (ocfs2_clusterinfo_valid(osb)) {
2170+
/*
2171+
* ci_stack and ci_cluster in ocfs2_cluster_info may not be null
2172+
* terminated, so make sure no overflow happens here by using
2173+
* memcpy. Destination strings will always be null terminated
2174+
* because osb is allocated using kzalloc.
2175+
*/
21702176
osb->osb_stackflags =
21712177
OCFS2_RAW_SB(di)->s_cluster_info.ci_stackflags;
2172-
strlcpy(osb->osb_cluster_stack,
2178+
memcpy(osb->osb_cluster_stack,
21732179
OCFS2_RAW_SB(di)->s_cluster_info.ci_stack,
2174-
OCFS2_STACK_LABEL_LEN + 1);
2180+
OCFS2_STACK_LABEL_LEN);
21752181
if (strlen(osb->osb_cluster_stack) != OCFS2_STACK_LABEL_LEN) {
21762182
mlog(ML_ERROR,
21772183
"couldn't mount because of an invalid "
@@ -2180,9 +2186,9 @@ static int ocfs2_initialize_super(struct super_block *sb,
21802186
status = -EINVAL;
21812187
goto bail;
21822188
}
2183-
strlcpy(osb->osb_cluster_name,
2189+
memcpy(osb->osb_cluster_name,
21842190
OCFS2_RAW_SB(di)->s_cluster_info.ci_cluster,
2185-
OCFS2_CLUSTER_NAME_LEN + 1);
2191+
OCFS2_CLUSTER_NAME_LEN);
21862192
} else {
21872193
/* The empty string is identical with classic tools that
21882194
* don't know about s_cluster_info. */

0 commit comments

Comments
 (0)