* [PATCH] module: Fix kernel panic when a symbol st_shndx is out of bounds
@ 2025-12-30 18:32 Ihor Solodrai
2026-01-12 14:37 ` Petr Pavlu
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Ihor Solodrai @ 2025-12-30 18:32 UTC (permalink / raw)
To: Luis Chamberlain, Petr Pavlu, Daniel Gomez, Nathan Chancellor,
Alexei Starovoitov, Daniel Borkmann, Andrii Nakryiko,
Martin KaFai Lau, Eduard Zingerman
Cc: linux-kernel, linux-modules, bpf, linux-kbuild, llvm
The module loader doesn't check for bounds of the ELF section index in
simplify_symbols():
for (i = 1; i < symsec->sh_size / sizeof(Elf_Sym); i++) {
const char *name = info->strtab + sym[i].st_name;
switch (sym[i].st_shndx) {
case SHN_COMMON:
[...]
default:
/* Divert to percpu allocation if a percpu var. */
if (sym[i].st_shndx == info->index.pcpu)
secbase = (unsigned long)mod_percpu(mod);
else
/** HERE --> **/ secbase = info->sechdrs[sym[i].st_shndx].sh_addr;
sym[i].st_value += secbase;
break;
}
}
A symbol with an out-of-bounds st_shndx value, for example 0xffff
(known as SHN_XINDEX or SHN_HIRESERVE), may cause a kernel panic:
BUG: unable to handle page fault for address: ...
RIP: 0010:simplify_symbols+0x2b2/0x480
...
Kernel panic - not syncing: Fatal exception
This can happen when module ELF is legitimately using SHN_XINDEX or
when it is corrupted.
Add a bounds check in simplify_symbols() to validate that st_shndx is
within the valid range before using it.
This issue was discovered due to a bug in llvm-objcopy, see relevant
discussion for details [1].
[1] https://lore.kernel.org/linux-modules/20251224005752.201911-1-ihor.solodrai@linux.dev/
Signed-off-by: Ihor Solodrai <ihor.solodrai@linux.dev>
---
kernel/module/main.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/kernel/module/main.c b/kernel/module/main.c
index 710ee30b3bea..5bf456fad63e 100644
--- a/kernel/module/main.c
+++ b/kernel/module/main.c
@@ -1568,6 +1568,13 @@ static int simplify_symbols(struct module *mod, const struct load_info *info)
break;
default:
+ if (sym[i].st_shndx >= info->hdr->e_shnum) {
+ pr_err("%s: Symbol %s has an invalid section index %u (max %u)\n",
+ mod->name, name, sym[i].st_shndx, info->hdr->e_shnum - 1);
+ ret = -ENOEXEC;
+ break;
+ }
+
/* Divert to percpu allocation if a percpu var. */
if (sym[i].st_shndx == info->index.pcpu)
secbase = (unsigned long)mod_percpu(mod);
--
2.52.0
^ permalink raw reply related [flat|nested] 4+ messages in thread* Re: [PATCH] module: Fix kernel panic when a symbol st_shndx is out of bounds
2025-12-30 18:32 [PATCH] module: Fix kernel panic when a symbol st_shndx is out of bounds Ihor Solodrai
@ 2026-01-12 14:37 ` Petr Pavlu
2026-02-20 15:55 ` Daniel Gomez
2026-02-24 18:34 ` Sami Tolvanen
2 siblings, 0 replies; 4+ messages in thread
From: Petr Pavlu @ 2026-01-12 14:37 UTC (permalink / raw)
To: Ihor Solodrai
Cc: Luis Chamberlain, Daniel Gomez, Nathan Chancellor,
Alexei Starovoitov, Daniel Borkmann, Andrii Nakryiko,
Martin KaFai Lau, Eduard Zingerman, linux-kernel, linux-modules,
bpf, linux-kbuild, llvm
On 12/30/25 7:32 PM, Ihor Solodrai wrote:
> The module loader doesn't check for bounds of the ELF section index in
> simplify_symbols():
>
> for (i = 1; i < symsec->sh_size / sizeof(Elf_Sym); i++) {
> const char *name = info->strtab + sym[i].st_name;
>
> switch (sym[i].st_shndx) {
> case SHN_COMMON:
>
> [...]
>
> default:
> /* Divert to percpu allocation if a percpu var. */
> if (sym[i].st_shndx == info->index.pcpu)
> secbase = (unsigned long)mod_percpu(mod);
> else
> /** HERE --> **/ secbase = info->sechdrs[sym[i].st_shndx].sh_addr;
> sym[i].st_value += secbase;
> break;
> }
> }
>
> A symbol with an out-of-bounds st_shndx value, for example 0xffff
> (known as SHN_XINDEX or SHN_HIRESERVE), may cause a kernel panic:
>
> BUG: unable to handle page fault for address: ...
> RIP: 0010:simplify_symbols+0x2b2/0x480
> ...
> Kernel panic - not syncing: Fatal exception
>
> This can happen when module ELF is legitimately using SHN_XINDEX or
> when it is corrupted.
>
> Add a bounds check in simplify_symbols() to validate that st_shndx is
> within the valid range before using it.
>
> This issue was discovered due to a bug in llvm-objcopy, see relevant
> discussion for details [1].
>
> [1] https://lore.kernel.org/linux-modules/20251224005752.201911-1-ihor.solodrai@linux.dev/
>
> Signed-off-by: Ihor Solodrai <ihor.solodrai@linux.dev>
Reviewed-by: Petr Pavlu <petr.pavlu@suse.com>
--
Thanks,
Petr
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [PATCH] module: Fix kernel panic when a symbol st_shndx is out of bounds
2025-12-30 18:32 [PATCH] module: Fix kernel panic when a symbol st_shndx is out of bounds Ihor Solodrai
2026-01-12 14:37 ` Petr Pavlu
@ 2026-02-20 15:55 ` Daniel Gomez
2026-02-24 18:34 ` Sami Tolvanen
2 siblings, 0 replies; 4+ messages in thread
From: Daniel Gomez @ 2026-02-20 15:55 UTC (permalink / raw)
To: Ihor Solodrai
Cc: Luis Chamberlain, Petr Pavlu, Nathan Chancellor,
Alexei Starovoitov, Daniel Borkmann, Andrii Nakryiko,
Martin KaFai Lau, Eduard Zingerman, linux-kernel, linux-modules,
bpf, linux-kbuild, llvm
On 2025-12-30 10:32, Ihor Solodrai wrote:
> The module loader doesn't check for bounds of the ELF section index in
> simplify_symbols():
>
> for (i = 1; i < symsec->sh_size / sizeof(Elf_Sym); i++) {
> const char *name = info->strtab + sym[i].st_name;
>
> switch (sym[i].st_shndx) {
> case SHN_COMMON:
>
> [...]
>
> default:
> /* Divert to percpu allocation if a percpu var. */
> if (sym[i].st_shndx == info->index.pcpu)
> secbase = (unsigned long)mod_percpu(mod);
> else
> /** HERE --> **/ secbase = info->sechdrs[sym[i].st_shndx].sh_addr;
> sym[i].st_value += secbase;
> break;
> }
> }
>
> A symbol with an out-of-bounds st_shndx value, for example 0xffff
> (known as SHN_XINDEX or SHN_HIRESERVE), may cause a kernel panic:
>
> BUG: unable to handle page fault for address: ...
> RIP: 0010:simplify_symbols+0x2b2/0x480
> ...
> Kernel panic - not syncing: Fatal exception
>
> This can happen when module ELF is legitimately using SHN_XINDEX or
> when it is corrupted.
>
> Add a bounds check in simplify_symbols() to validate that st_shndx is
> within the valid range before using it.
>
> This issue was discovered due to a bug in llvm-objcopy, see relevant
> discussion for details [1].
>
> [1] https://lore.kernel.org/linux-modules/20251224005752.201911-1-ihor.solodrai@linux.dev/
>
> Signed-off-by: Ihor Solodrai <ihor.solodrai@linux.dev>
Reviewed-by: Daniel Gomez <da.gomez@samsung.com>
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [PATCH] module: Fix kernel panic when a symbol st_shndx is out of bounds
2025-12-30 18:32 [PATCH] module: Fix kernel panic when a symbol st_shndx is out of bounds Ihor Solodrai
2026-01-12 14:37 ` Petr Pavlu
2026-02-20 15:55 ` Daniel Gomez
@ 2026-02-24 18:34 ` Sami Tolvanen
2 siblings, 0 replies; 4+ messages in thread
From: Sami Tolvanen @ 2026-02-24 18:34 UTC (permalink / raw)
To: Luis Chamberlain, Petr Pavlu, Daniel Gomez, Nathan Chancellor,
Alexei Starovoitov, Daniel Borkmann, Andrii Nakryiko,
Martin KaFai Lau, Eduard Zingerman, Ihor Solodrai
Cc: linux-kernel, linux-modules, bpf, linux-kbuild, llvm
On Tue, 30 Dec 2025 10:32:08 -0800, Ihor Solodrai wrote:
> The module loader doesn't check for bounds of the ELF section index in
> simplify_symbols():
>
> for (i = 1; i < symsec->sh_size / sizeof(Elf_Sym); i++) {
> const char *name = info->strtab + sym[i].st_name;
>
> switch (sym[i].st_shndx) {
> case SHN_COMMON:
>
> [...]
Applied to modules-next, thanks!
[1/1] module: Fix kernel panic when a symbol st_shndx is out of bounds
commit: f9d69d5e7bde2295eb7488a56f094ac8f5383b92
Best regards,
Sami
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-02-24 18:34 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-12-30 18:32 [PATCH] module: Fix kernel panic when a symbol st_shndx is out of bounds Ihor Solodrai
2026-01-12 14:37 ` Petr Pavlu
2026-02-20 15:55 ` Daniel Gomez
2026-02-24 18:34 ` Sami Tolvanen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox