CVE-2026-74485: binfmt_misc: reject a flag character as the field delimiter
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1819f82dee766c58295ecaacdac02cdf6837d7a4, 1853e95c9bfe69ef1dd862b3f551e68f4a1b76cc, 840bb9c49c3e75fb32b593d67ab32f6b77122262; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1819f82dee766c58295ecaacdac02cdf6837d7a4, 1853e95c9bfe69ef1dd862b3f551e68f4a1b76cc, 840bb9c49c3e75fb32b593d67ab32f6b77122262; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: binfmt_misc: reject a flag character as the field delimiter The registration string starts with a user chosen delimiter that separates the individual fields. So that the field parsers terminate even on a truncated string create_entry() pads the buffer with that same delimiter: memset(buf + count, del, 8); Most fields are scanned for the delimiter with strchr()/scanarg() and happily stop on the padding. The flags field is different: instead of scanning for the delimiter check_special_flags() consumes the flag characters 'P', 'O', 'C' and 'F' and stops at the first byte that is none of them, relying on the trailing delimiter to end the scan. If the delimiter is itself a flag character the padding no longer acts as a terminator. The scan swallows all eight padding bytes and keeps reading past the end of the allocation until it hits a byte that is not a flag character. For example registering PaPEPPxPPiP with 'P' as the delimiter (name "a", type extension, magic "x", interpreter "i", empty flags) leaves the flag scan running off the end of the buffer. The registration is rejected in the end because the parser does not stop exactly at buf + count, but only after the out of bounds read has already happened. With an unlucky allocation layout the scan can walk into an unmapped page; under KASAN it is reported as a slab out of bounds read. binfmt_misc mounts are available to unprivileged users in a user namespace so the read is reachable without privileges. Reject a delimiter that is one of the flag characters up front. Such a registration was always rejected anyway, only after the out of bounds read, so no valid registration string changes meaning.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.12affected
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 96bd5d4fea2970b9b08265293ca7a10b9b27c0fdaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 9970e094e5d60f0d66914bf9a97d1ef19107ebf5affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b29e3c1f375c1296362d219ff38bceddf2d2a88aaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 1819f82dee766c58295ecaacdac02cdf6837d7a4affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 1853e95c9bfe69ef1dd862b3f551e68f4a1b76ccaffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 840bb9c49c3e75fb32b593d67ab32f6b77122262affected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 9a2d87db3898b5993b64fd258d0334e0eba9ee0daffected · git
- 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 8e85d50ba1117fd446bf9a250bd8a97d48384bdcaffected · git
- before 2.6.12not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.8-1 | 7.1.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74481Aug 15, 2026 · mm/page_reporting: use system_freezable_wq to fix UAF during suspend31Monitor
- ← EarlierCVE-2026-74482Aug 15, 2026 · mm/huge_memory: unlock i_mmap_rwsem before releasing after-split folios31Monitor
- Later →CVE-2026-74488Aug 15, 2026 · wifi: mwifiex: use the subframe length when parsing A-MSDU TDLS frames35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1819f82dee766c58295ecaacdac02cdf6837d7a4 | Vendor (CNA) |
| Linux Linux | 1853e95c9bfe69ef1dd862b3f551e68f4a1b76cc | Vendor (CNA) |
| Linux Linux | 840bb9c49c3e75fb32b593d67ab32f6b77122262 | Vendor (CNA) |
| Linux Linux | 8e85d50ba1117fd446bf9a250bd8a97d48384bdc | Vendor (CNA) |
| Linux Linux | 96bd5d4fea2970b9b08265293ca7a10b9b27c0fd | Vendor (CNA) |
| Linux Linux | 9970e094e5d60f0d66914bf9a97d1ef19107ebf5 | Vendor (CNA) |
| Linux Linux | 9a2d87db3898b5993b64fd258d0334e0eba9ee0d | Vendor (CNA) |
| Linux Linux | b29e3c1f375c1296362d219ff38bceddf2d2a88a | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.152.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0854 · Aug 19, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1853e95c9bfe69ef1dd862b3f551e68f4a1b76cc
- git.kernel.org/stable/c/840bb9c49c3e75fb32b593d67ab32f6b77122262
- git.kernel.org/stable/c/8e85d50ba1117fd446bf9a250bd8a97d48384bdc
- git.kernel.org/stable/c/96bd5d4fea2970b9b08265293ca7a10b9b27c0fd
- git.kernel.org/stable/c/9970e094e5d60f0d66914bf9a97d1ef19107ebf5
- git.kernel.org/stable/c/9a2d87db3898b5993b64fd258d0334e0eba9ee0d
- git.kernel.org/stable/c/b29e3c1f375c1296362d219ff38bceddf2d2a88a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.