binfmt_elf_fdpic: only honour the first PT_INTERP
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 89b9121c3b0162655fc2f190b714ae64f1aa8cae| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
binfmt_elf_fdpic: only honour the first PT_INTERP
The program header scan handles PT_INTERP from a switch nested in the scan loop, so its break leaves the switch and not the loop. A binary carrying more than one PT_INTERP runs the case again and overwrites both interpreter_name and interpreter. The previous name allocation leaks and so does the previous interpreter reference, along with the write denial open_exec() took on it. The denial is never released, so the file stays unwritable for as long as the system runs.
An unprivileged caller reaches this with a crafted binary and repeats it at will. binfmt_elf stops at the first PT_INTERP. Do the same here.
The flaw dates back to the driver's introduction in the pre-git history tree introduced in v2.6.11 by 91808d6ebe39 ("[PATCH] FRV: Add FDPIC ELF binary format driver").
From the CVE record · Linux
The Linux kernel's binfmt_elf_fdpic handler mishandles binaries with multiple PT_INTERP entries. A local, unprivileged caller can run a crafted binary repeatedly, leaking resources and leaving an interpreter file unwritable until the system stops.
Operators running Linux kernels with the binfmt_elf_fdpic handler should check their exposure; the flaw dates back to the driver's introduction in v2.6.11.