BUG: unable to handle kernel NULL pointer dereference in strrchr

Status: upstream: reported C repro on 2026/11/20 12:49
Subsystems: ext4
Labels: prio:normal
[Documentation on labels]
Reported-by: syzbot+1d23ad199a3bfd6f9149@syzkaller.appspotmail.com
First crash: 4d06h, last: 54m
✨ AI cause bisection: introduced by (AI job) :
commit 98f18c76c2c3089183c35d2c33e468ad6c03d86b
Author: Eric Sandeen <sandeen@redhat.com>
Date: Sun Feb 23 19:57:41 2025 +0000

  ext2: create ext2_msg_fc for use during parsing

✨ AI-generated root cause summary:

In fs/ext2/super.c, ext2_msg_fc() formats log messages for filesystem context operations. When fc->purpose != FS_CONTEXT_FOR_RECONFIGURE, it unconditionally executes strrchr(fc->source, '/') without verifying that fc->source is non-NULL. During filesystem configuration via the new mount API (e.g., fsopen() followed by fsconfig()), fc->source starts as NULL and options can be parsed in any order. Specifying an option that triggers ext2_msg_fc() (such as "dax", "nobh", or "reservation") prior to supplying the "source" parameter passes a NULL pointer to strrchr(), causing a kernel NULL pointer dereference.

▶ ▼ ✨ Full AI root cause analysis
Based on kernel commit fa2933aac170:

Root Cause Analysis

1. Relevant Functions, Structs, and Files

2. Technical Mechanism and Lifecycle Violation

When a filesystem context is created for a new mount (via fsopen("ext2", ...)), fc->purpose is initialized to FS_CONTEXT_FOR_MOUNT, and fc->source is initially NULL. fc->source is only populated when userspace explicitly supplies the "source" parameter (handled by vfs_parse_fs_param_source()).

Under the mount API (fsconfig), userspace is permitted to configure filesystem mount parameters in arbitrary order before issuing FSCONFIG_CMD_CREATE. Furthermore, userspace may configure parameters without ever providing a "source" parameter.

In fs/ext2/super.c, ext2_msg_fc() formats and emits log messages during mount context processing:

static void ext2_msg_fc(struct fs_context *fc, const char *prefix,
			const char *fmt, ...)
{
	struct va_format vaf;
	va_list args;
	const char *s_id;

	if (fc->purpose == FS_CONTEXT_FOR_RECONFIGURE) {
		s_id = fc->root->d_sb->s_id;
	} else {
		/* get last path component of source */
		s_id = strrchr(fc->source, '/');
		if (s_id)
			s_id++;
		else
			s_id = fc->source;
	}
...

When fc->purpose != FS_CONTEXT_FOR_RECONFIGURE (e.g. for any new mount context):

  1. ext2_msg_fc() enters the else branch and unconditionally executes s_id = strrchr(fc->source, '/'); without verifying whether fc->source is NULL.
  2. Several options in ext2_parse_param() invoke ext2_msg_fc() to log informational or deprecation/warning messages:
    • Opt_dax: ext2_msg_fc(fc, KERN_WARNING, "DAX support has been removed. dax option ignored."); (line 598)
    • Opt_xip: ext2_msg_fc(fc, KERN_WARNING, "DAX support has been removed. xip option ignored."); (line 595)
    • Opt_nobh: ext2_msg_fc(fc, KERN_INFO, "nobh option not supported\n"); (line 568)
    • Opt_reservation: ext2_msg_fc(fc, KERN_INFO, "reservations ON/OFF"); (lines 620, 623)
    • Unsupported user_xattr, acl, or quota configurations (lines 579, 591, 614)
  3. If userspace sends an fsconfig() request for one of these options (such as "dax" via FSCONFIG_SET_FLAG) before "source" has been configured, fc->source is NULL.
  4. strrchr(NULL, '/') is invoked, immediately reading through r0 = 0x00000000 (ldrb r2, [r0], #1 in arch/arm/lib/strrchr.S:16), resulting in the reported kernel NULL pointer dereference crash.
▶ ▼ ✨ AI Jobs (3)
ID Workflow Result Correct Bug Created Started Finished Revision
9bf26eba repro-c Reproduced: ✅ ❓ BUG: unable to handle kernel NULL pointer dereference in strrchr 2026/11/20 12:12 2026/11/20 12:12 2026/11/20 12:32 625aa117
f0a661eb bisect-cause IsRelease: ❌ ❓ BUG: unable to handle kernel NULL pointer dereference in strrchr 2026/11/20 04:47 2026/11/20 04:47 2026/11/20 05:11 229865fb
0b714462 assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ❌ FuzzingArtifact: ❌ MemoryCorruption: ❌ NetworkNeedsSetup: ❌ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ✅ VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ BUG: unable to handle kernel NULL pointer dereference in strrchr 2026/11/16 07:16 2026/11/16 07:16 2026/11/16 07:37 819ebe34
▶ ▼ Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [ext4?] BUG: unable to handle kernel NULL pointer dereference in strrchr 1 (2) 2026/11/20 13:07
▶ ▼ Similar bugs (3)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-5-15 KASAN: use-after-free Read in strrchr 19 syz, C 5 18d 20d 0/2 upstream: reported C repro on 2026/10/31 08:26
android-5-10 KASAN: use-after-free Read in strrchr 19 syz, C 5 9d04h 27d 0/2 upstream: reported C repro on 2026/10/24 05:39
android-6-12 KASAN: slab-use-after-free Read in strrchr origin:lts 19 syz, C 4 15d 38d 0/1 premoderation: reported C repro on 2026/10/13 01:47
▶ ▼ Last patch testing requests (1)
Created Duration User Patch Repo Result
2026/11/20 12:33 15m retest repro https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux 65e4fd942f72a9dba0e4e257290c4fa1aa756854 report job log log

Sample crash report:
8<--- cut here ---
Unable to handle kernel NULL pointer dereference at virtual address 00000000 when read
[00000000] *pgd=86b45003, *pmd=df702003
Internal error: Oops: 205 [#1] SMP ARM
Modules linked in:
CPU: 0 UID: 0 PID: 4221 Comm: syz-executor704 Not tainted syzkaller #0 PREEMPT 
Hardware name: ARM-Versatile Express
PC is at strrchr+0x4/0x20 arch/arm/lib/strrchr.S:16
LR is at ext2_msg_fc+0x64/0xbc fs/ext2/super.c:94
pc : [<81be3be4>]    lr : [<80207988>]    psr: 80000013
sp : df969ed0  ip : 00000000  fp : df969efc
r10: 8665ce00  r9 : 86c5a600  r8 : 8665ce00
r7 : 00000000  r6 : 825897f0  r5 : 82533520  r4 : 00000000
r3 : 00000000  r2 : 00000000  r1 : 0000002f  r0 : 00000000
Flags: Nzcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
Control: 30c5387d  Table: 86801300  DAC: fffffffd
Register r0 information: NULL pointer
Register r1 information: non-paged memory
Register r2 information: NULL pointer
Register r3 information: NULL pointer
Register r4 information: NULL pointer
Register r5 information: non-slab/vmalloc memory
Register r6 information: non-slab/vmalloc memory
Register r7 information: NULL pointer
Register r8 information: slab filp start 8665ce00 pointer offset 0 size 128
Register r9 information: slab kmalloc-cg-128 start 86c5a600 pointer offset 0 size 128
Register r10 information: slab filp start 8665ce00 pointer offset 0 size 128
Register r11 information: 2-page vmalloc region starting at 0xdf968000 allocated at kernel_clone+0xc4/0x440 kernel/fork.c:2798
Register r12 information: NULL pointer
Process syz-executor704 (pid: 4221, stack limit = 0xdf968000)
Stack: (0xdf969ed0 to 0xdf96a000)
9ec0:                                     00000000 00000000 00000000 9b02fc30
9ee0: 86c7ab80 86c5a600 86c7ab80 fffffdf9 df969f34 df969f08 80791374 80207934
9f00: 825897f0 0000006a 00000000 00000000 00000001 00000000 fffffdf9 9b02fc30
9f20: 86c5a600 df969f60 df969f5c df969f38 80632b70 8079114c 80501748 805015b0
9f40: 00000000 00000000 00000000 86c5a604 df969fa4 df969f60 80634f3c 80632ab8
9f60: 86801c00 00000001 00000000 00000000 00000000 9b02fc30 00000000 00000000
9f80: 00000002 00000001 000001af 8020029c 84563300 000001af 00000000 df969fa8
9fa0: 80200060 80634c2c 00000000 00000002 00000003 00000000 000653e0 00000000
9fc0: 00000000 00000002 00000001 000001af 00000000 7eb39e0c 00000002 00000000
9fe0: 7eb39c90 7eb39c80 00010330 00027e10 60000010 00000003 00000000 00000000
Call trace: 
[<80207924>] (ext2_msg_fc) from [<80791374>] (ext2_parse_param+0x234/0x2dc fs/ext2/super.c:598)
 r3:0000006a r2:825897f0
 r6:fffffdf9 r5:86c7ab80 r4:86c5a600
[<80791140>] (ext2_parse_param) from [<80632b70>] (vfs_parse_fs_param+0xc4/0x13c fs/fs_context.c:132)
 r5:df969f60 r4:86c5a600
[<80632aac>] (vfs_parse_fs_param) from [<80634f3c>] (vfs_fsconfig_locked fs/fsopen.c:306 [inline])
[<80632aac>] (vfs_parse_fs_param) from [<80634f3c>] (__do_sys_fsconfig fs/fsopen.c:466 [inline])
[<80632aac>] (vfs_parse_fs_param) from [<80634f3c>] (sys_fsconfig+0x31c/0x514 fs/fsopen.c:353)
 r6:86c5a604 r5:00000000 r4:00000000
[<80634c20>] (sys_fsconfig) from [<80200060>] (ret_fast_syscall+0x0/0x1c arch/arm/mm/proc-v7.S:67)
Exception stack(0xdf969fa8 to 0xdf969ff0)
9fa0:                   00000000 00000002 00000003 00000000 000653e0 00000000
9fc0: 00000000 00000002 00000001 000001af 00000000 7eb39e0c 00000002 00000000
9fe0: 7eb39c90 7eb39c80 00010330 00027e10
 r10:000001af r9:84563300 r8:8020029c r7:000001af r6:00000001 r5:00000002
 r4:00000000
Code: 00000000 00000000 00000000 e3a03000 (e4d02001) 
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
   c:	e3a03000 	mov	r3, #0
* 10:	e4d02001 	ldrb	r2, [r0], #1 <-- trapping instruction

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/11/20 12:48 https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux 65e4fd942f72 819ebe34 .config console log report C ci-qemu2-arm32 BUG: unable to handle kernel NULL pointer dereference in strrchr
2026/11/16 07:16 https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux master fa2933aac170 819ebe34 .config console log report info [disk image (non-bootable)] [vmlinux] [kernel image] ci-qemu2-arm32 BUG: unable to handle kernel NULL pointer dereference in strrchr
* Struck through repros no longer work on HEAD.