CVE-2026-68151

binfmt_elf_fdpic: only honour the first PT_INTERP

N/A
Published: August 10, 2026 at 11:59 AM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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").

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.12 ≤ v < 5.10.2652.6.12 ≤ v < 5.15.2162.6.12 ≤ v < 6.1.1832.6.12 ≤ v < 6.12.1012.6.12 ≤ v < 6.18.422.6.12 ≤ v < 6.6.1482.6.12 ≤ v < 7.1.62.6.12 ≤ v < 7.21da177e4c3f41524e886b7f1b8a0c1fc7321cac22.6.12
Vendor states this is fixed in 21eaf5594a33d16343a011c752624099c30e918f (fixed)
Vendor states this is fixed in 3349ef6a366a61d631f6a263d12cea240957719d (fixed)
Vendor states this is fixed in 3c31397b0a75310217f1f2f3c7bdfd8af67aec4c (fixed)
Vendor states this is fixed in 69ecc199880bf7e8d06224c82dc411d18f9285f8 (fixed)
Vendor states this is fixed in 849a7bd9d266e43a457db5c6b322600f916a2127 (fixed)
Vendor states this is fixed in 89b9121c3b0162655fc2f190b714ae64f1aa8cae (fixed)
Vendor states this is fixed in 9854538349aaf6fb88ed33b56987954ac1716151 (fixed)
Vendor states this is fixed in e4563e07ef5c938d5332c5c44721db976f214bc6 (fixed)
Vendor states this is fixed in 2.6.12 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card