module: Fix kernel panic when a symbol st_shndx is out of bounds
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 6ba6957c640f58dc8ef046981a045da43e47ea23| No fix yet |
| Linux Linux |
|
|
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:
From the CVE record · Linux
The Linux kernel module loader does not check whether a symbol’s ELF section index is in bounds. Loading a module with an out-of-range index, whether from a valid ELF feature or corruption, can cause a kernel panic. An attacker would need to cause such a module to be loaded; the input does not specify authentication requirements.
Engineers running Linux kernels should check whether their kernel includes the module-loader bounds check; affected versions are not specified.