In the Linux kernel, the following vulnerability has been resolved: fs/statmount: fix slab out-of-bounds write in statmount_mnt_idmap… (CVE-2026-64074)
In the Linux kernel, the following vulnerability has been resolved: fs/statmount: fix slab out-of-bounds write in statmount_mnt_idmap statmount_mnt_idmap() writes one mapping with seq_printf() and then manually advances seq->count to include the NUL separator. If seq_printf() overflows, seq_set_overflow() sets seq->count to seq->size. The manual seq->count++ changes this to seq->size + 1. seq_has_overflowed() then no longer detects the overflow. The corrupted count returns to statmount_string(), which later executes: seq->buf[seq->count++] = '\0'; This causes a 1-byte NULL out-of-bounds write on the dynamically allocated seq buffer. Fix this by checking for overflow immediately after seq_printf().
AI Analysis
Technical Summary
The Linux kernel contained a vulnerability in the fs/statmount component where statmount_mnt_idmap() improperly handled the seq->count field after a seq_printf() call. If seq_printf() overflowed, seq_set_overflow() set seq->count to seq->size, but a subsequent manual increment changed it to seq->size + 1, causing seq_has_overflowed() to fail to detect the overflow. This led to a one-byte NULL out-of-bounds write on the seq buffer when statmount_string() executed seq->buf[seq->count++] = '\0'. The flaw was fixed by adding an immediate overflow check after seq_printf().
Potential Impact
This vulnerability results in a one-byte out-of-bounds write to kernel memory, which could potentially corrupt memory and lead to undefined behavior or kernel instability. No known exploits in the wild have been reported. The impact is limited to a minor memory corruption issue within the kernel's statmount code.
Mitigation Recommendations
A fix has been implemented in the Linux kernel source code to check for overflow immediately after seq_printf() in statmount_mnt_idmap(). Users should apply the official kernel updates or patches that include this fix once available. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: fs/statmount: fix slab out-of-bounds write in statmount_mnt_idmap… (CVE-2026-64074)
Description
In the Linux kernel, the following vulnerability has been resolved: fs/statmount: fix slab out-of-bounds write in statmount_mnt_idmap statmount_mnt_idmap() writes one mapping with seq_printf() and then manually advances seq->count to include the NUL separator. If seq_printf() overflows, seq_set_overflow() sets seq->count to seq->size. The manual seq->count++ changes this to seq->size + 1. seq_has_overflowed() then no longer detects the overflow. The corrupted count returns to statmount_string(), which later executes: seq->buf[seq->count++] = '\0'; This causes a 1-byte NULL out-of-bounds write on the dynamically allocated seq buffer. Fix this by checking for overflow immediately after seq_printf().
CVSS v3.1
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel contained a vulnerability in the fs/statmount component where statmount_mnt_idmap() improperly handled the seq->count field after a seq_printf() call. If seq_printf() overflowed, seq_set_overflow() set seq->count to seq->size, but a subsequent manual increment changed it to seq->size + 1, causing seq_has_overflowed() to fail to detect the overflow. This led to a one-byte NULL out-of-bounds write on the seq buffer when statmount_string() executed seq->buf[seq->count++] = '\0'. The flaw was fixed by adding an immediate overflow check after seq_printf().
Potential Impact
This vulnerability results in a one-byte out-of-bounds write to kernel memory, which could potentially corrupt memory and lead to undefined behavior or kernel instability. No known exploits in the wild have been reported. The impact is limited to a minor memory corruption issue within the kernel's statmount code.
Mitigation Recommendations
A fix has been implemented in the Linux kernel source code to check for overflow immediately after seq_printf() in statmount_mnt_idmap(). Users should apply the official kernel updates or patches that include this fix once available. Patch status is not explicitly confirmed in the provided data; check the vendor or Linux kernel advisories for the current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-q6fc-4c58-35pf
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64074"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a92a4a8d598912bf10
Added to database: 07/19/2026, 19:38:17 UTC
Last enriched: 07/19/2026, 19:51:19 UTC
Last updated: 07/20/2026, 19:41:22 UTC
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.