module: Fix kernel panic when a symbol st_shndx is out of bounds
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.203, 6.1.168, 6.6.131, 6.12.80, 6.18.21, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: module: Fix kernel panic when a symbol st_shndx is out of bounds 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/
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 5d16f519b6eb1d071807e57efe0df2baa8d32ad6; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 4bbdb0e48176fd281c2b9a211b110db6fd94e175; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 082f15d2887329e0f43fd3727e69365f5bfe5d2c; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in ec2b22a58073f80739013588af448ff6e2ab906f; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in ef75dc1401d8e797ee51559a0dd0336c225e1776; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in 6ba6957c640f58dc8ef046981a045da43e47ea23; From 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · fixed in f9d69d5e7bde2295eb7488a56f094ac8f5383b92
- Linux Linux
2.6.12
- KernelLinux
From 2.6.12 · fixed in 5.15.203; From 5.16.0 · fixed in 6.1.168; From 6.2.0 · fixed in 6.6.131; From 6.7.0 · fixed in 6.12.80; From 6.13.0 · fixed in 6.18.21; From 6.19.0 · fixed in 6.19.11
References 7
git.kernel.org
- stable/c/5d16f519b6eb1d071807e57efe0df2baa8d32ad6
- stable/c/4bbdb0e48176fd281c2b9a211b110db6fd94e175
- stable/c/082f15d2887329e0f43fd3727e69365f5bfe5d2c
- stable/c/ec2b22a58073f80739013588af448ff6e2ab906f
- stable/c/ef75dc1401d8e797ee51559a0dd0336c225e1776
- stable/c/6ba6957c640f58dc8ef046981a045da43e47ea23
- stable/c/f9d69d5e7bde2295eb7488a56f094ac8f5383b92