Re: [PATCH 6.18 000/641] 6.18.14-rc2 review

[Guenter Roeck]

Hi,

On 2/25/26 07:51, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.18.14 release.
> There are 641 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Fri, 27 Feb 2026 15:17:08 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> 	https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.18.14-rc2.gz
> or in the git tree and branch at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.18.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
> -------------
> Pseudo-Shortlog of commits:
...
> Petr Mladek <pmladek@xxxxxxxx>
>      kallsyms/bpf: rename __bpf_address_lookup() to bpf_address_lookup()

Unfortunately, this patch does a bit more than it advertises:
The shim function it removes used to set *modname to NULL if
the module name was not found. This code is no longer necessary upstream
since commit fda024fb6476 ("kallsyms: clean up modname and modbuildid
initialization in kallsyms_lookup_buildid()") unconditionally initializes
*modname to NULL.

Unfortunately, commit fda024fb6476 was not back-ported to v6.18.y or v6.19.y.
This results in kernel crashes if the symbol is a bpf address.

[ 5393.147564] Oops: general protection fault, probably for non-canonical address 0x776d477193e1c300: 0000 [#1] SMP NOPTI
[ 5393.147567] CPU: 7 UID: 0 PID: 489696 Comm: step_worker Kdump: loaded Tainted: P S   U     O     N  6.18.14-smp-DEV #1 NONE
[ 5393.147570] Tainted: [P]=PROPRIETARY_MODULE, [S]=CPU_OUT_OF_SPEC, [U]=USER, [O]=OOT_MODULE, [N]=TEST
[ 5393.147571] Hardware name: Google LLC Indus/Indus_QC_03, BIOS 30.116.4 08/29/2025
[ 5393.147571] RIP: 0010:string+0xbc/0x100
[ 5393.147574] Code: 44 88 11 eb e0 31 f6 81 f9 00 00 01 00 73 05 e9 0a 1e 00 00 89 ce c1 fe 10 45 31 c9 eb 08 49 ff c1 44 39 ce 74 39 4e 8d 04 0f <46> 0f b6 14 08 45 84 d2 74 20 49 39 d0 73 e5 45 88 10 eb e0 44 89
[ 5393.147575] RSP: 0018:ffff9709489fc498 EFLAGS: 00010046
[ 5393.147576] RAX: 776d477193e1c300 RBX: ffffffff973ae731 RCX: ffffffffffff0a00
[ 5393.147577] RDX: ffff9709c89fc5df RSI: 00000000ffffffff RDI: ffff9709489fc5e2
[ 5393.147578] RBP: 0000000000000405 R08: ffff9709489fc5e2 R09: 0000000000000000
[ 5393.147579] R10: 0000000000000036 R11: 0000000000000002 R12: ffff9709489fc5e2
[ 5393.147580] R13: ffffffff973ae72f R14: ffff9709c89fc5df R15: ffff9709489fc530
[ 5393.147580] FS:  0000000000000000(0000) GS:ffff935966f63000(0000) knlGS:0000000000000000
[ 5393.147582] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 5393.147583] CR2: 0000562833e138a8 CR3: 00000006c94f5006 CR4: 00000000007726f0
[ 5393.147584] PKRU: 55555554
[ 5393.147584] Call Trace:
[ 5393.147585]  <IRQ>
[ 5393.147587]  [<ffffffff96c5d1c8>] vsnprintf+0x2f8/0x410
[ 5393.147591]  [<ffffffff96c5e736>] sprintf+0x66/0x90

Please apply commit fda024fb6476 to v6.18.y and v6.19.y to fix the problem.

Thanks,
Guenter