binfmt_misc: use exe_file_deny_write_access() for the interpreter clone
In the Linux kernel, the following vulnerability has been resolved: binfmt_misc: use exe_file_deny_write_access() for the interpreter clone For MISC_FMT_OPEN_FILE entries load_misc_binary() clones the registered interpreter file and denies write access to the clone via plain deny_write_access(). The clone is installed as bprm->interpreter and later released by the exec machinery through exe_file_allow_write_access() which skips the i_writecount increment for files with FMODE_FSNOTIFY_HSM set. The deny and allow side can therefore come to different conclusions when pre-content watches are in play: if a pre-content watch is added to the interpreter after registration every subsequent exec through that entry takes a write denial on the clone that is never paired with a write allowance, driving the interpreter inode's i_writecount further down with each exec and leaving the interpreter unwritable even after the entry and all its users are gone. Take the write denial via exe_file_deny_write_access() so both sides of the pairing base their decision on the same file mode, and propagate failure instead of silently ignoring it: an interpreter that is concurrently open for writing now fails the exec with ETXTBSY, exactly like an interpreter freshly opened via open_exec() would.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.18.44, 7.1.8
- CVEs
- CVE-2026-74486
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 23:00 UTC · Revision 1
Source evidence
binfmt_misc: use exe_file_deny_write_access() for the interpreter clone
core-osv · Original sourcePublished 15 Aug 2026, 12:27 UTC
In the Linux kernel, the following vulnerability has been resolved: binfmt_misc: use exe_file_deny_write_access() for the interpreter clone For MISC_FMT_OPEN_FILE entries load_misc_binary() clones the registered interpreter file and denies write access to the clone via plain deny_write_access(). The clone is installed as bprm->interpreter and later released by the exec machinery through exe_file_allow_write_access() which skips the i_writecount increment for files with FMODE_FSNOTIFY_HSM set. The deny and allow side can therefore come to different conclusions when pre-content watches are in play: if a pre-content watch is added to the interpreter after registration every subsequent exec through that entry takes a write denial on the clone that is never paired with a write allowance, driving the interpreter inode's i_writecount further down with each exec and leaving the interpreter unwritable even after the entry and all its users are gone. Take the write denial via exe_file_deny_write_access() so both sides of the pairing base their decision on the same file mode, and propagate failure instead of silently ignoring it: an interpreter that is concurrently open for writing now fails the exec with ETXTBSY, exactly like an interpreter freshly opened via open_exec() would.
osv:CVE-2026-74486
Kernel
Fixed versions: 6.18.44, 7.1.8
Complete source record
{
"id": "22e5ebde1f8a94cd490881813fd2914d570e9b3d3f6511e62896e34a2cd47f7b",
"url": "https://osv.dev/vulnerability/CVE-2026-74486",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "binfmt_misc: use exe_file_deny_write_access() for the interpreter clone",
"summary": "In the Linux kernel, the following vulnerability has been resolved: binfmt_misc: use exe_file_deny_write_access() for the interpreter clone For MISC_FMT_OPEN_FILE entries load_misc_binary() clones the registered interpreter file and denies write access to the clone via plain deny_write_access(). The clone is installed as bprm->interpreter and later released by the exec machinery through exe_file_allow_write_access() which skips the i_writecount increment for files with FMODE_FSNOTIFY_HSM set. The deny and allow side can therefore come to different conclusions when pre-content watches are in play: if a pre-content watch is added to the interpreter after registration every subsequent exec through that entry takes a write denial on the clone that is never paired with a write allowance, driving the interpreter inode's i_writecount further down with each exec and leaving the interpreter unwritable even after the entry and all its users are gone. Take the write denial via exe_file_deny_write_access() so both sides of the pairing base their decision on the same file mode, and propagate failure instead of silently ignoring it: an interpreter that is concurrently open for writing now fails the exec with ETXTBSY, exactly like an interpreter freshly opened via open_exec() would.",
"evidence": "osv:CVE-2026-74486",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.18.44",
"evidence": "/affected/1/ranges"
},
{
"value": "7.1.8",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-74486",
"aliases": [
"CVE-2026-74486"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "5b432413f7bbbc8b935138490a57be05c1921684"
},
{
"fixed": "c65eb018c12179b5e2c7afe1f0956298576fecec"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "bb4715098d8e340bbbdd3a874b31f89867c8067e"
},
{
"fixed": "2bd860b7e752a51185960143cab9fec7bf32c84e"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "c152be5adc0975c75cc4f50891c9072d52d60b47"
},
{
"fixed": "eea4b7c7711b1e425272d23352af157f45f4c3e3"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "bf5ed2ef5cdb7b47ce606e3d48ea6eb803b31503"
},
{
"fixed": "2fdf8b07bee5ef99ec77773a6be05fbb8ee5cdb9"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "483217fd6f7ccd98b3ed2531a54f75ed144b4499"
},
{
"fixed": "f1e7ea3c8e070f19771cdaef55bbeda1359ad490"
}
]
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "0357ef03c94ef835bd44a0658b8edb672a9dbf51"
},
{
"fixed": "255a758697da87a205e072e0cfc35897b8f743b1"
},
{
"fixed": "f0edbaf487e4653a680a7abb91c1df94cb7886aa"
},
{
"fixed": "fa5990ca8fd917003e526036bcc50413edb9722c"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-74486.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.14.0"
},
{
"fixed": "6.18.44"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.1.8"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-74486.json"
}
}
],
"modified": "2026-10-28T02:30:24.138610179Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/255a758697da87a205e072e0cfc35897b8f743b1",
"https://git.kernel.org/stable/c/2bd860b7e752a51185960143cab9fec7bf32c84e",
"https://git.kernel.org/stable/c/2fdf8b07bee5ef99ec77773a6be05fbb8ee5cdb9",
"https://git.kernel.org/stable/c/c65eb018c12179b5e2c7afe1f0956298576fecec",
"https://git.kernel.org/stable/c/eea4b7c7711b1e425272d23352af157f45f4c3e3",
"https://git.kernel.org/stable/c/f0edbaf487e4653a680a7abb91c1df94cb7886aa",
"https://git.kernel.org/stable/c/f1e7ea3c8e070f19771cdaef55bbeda1359ad490",
"https://git.kernel.org/stable/c/fa5990ca8fd917003e526036bcc50413edb9722c",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/74xxx/CVE-2026-74486.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-74486",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/74xxx/CVE-2026-74486.json"
}
},
"related_cves": [
{
"value": "CVE-2026-74486",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 490700,
"published_at": "2026-08-15T12:27:17.609+00:00"
}