LiveActive security incident?Get immediate response
CVE Record

CVE-2026-64074: fs/statmount: fix slab out-of-bounds write in statmount_mnt_idmap

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

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-64074 is a Linux kernel memory corruption flaw. A local authenticated user could trigger a one-byte out-of-bounds NULL write in statmount handling, potentially affecting confidentiality, integrity, and availability. The supplied CVSS score is 7.8, so prioritize affected Linux hosts where local users, shells, containers, or multi-tenant workloads exist.

Executive priority

Treat as high priority for Linux fleets with local user access or shared workloads. It is not currently documented as exploited in the supplied sources, but kernel memory corruption with high CVSS impact justifies prompt patch planning.

Technical view

The flaw is in fs/statmount, specifically statmount_mnt_idmap(). After seq_printf() overflows and sets seq->count to seq->size, later manual count advancement can hide the overflow. statmount_string() can then write a NUL byte beyond the allocated seq buffer. The fix checks overflow immediately after seq_printf().

Likely exposure

Exposure is limited to Linux systems running affected kernel versions identified by the CVE record. Risk is higher on shared servers, developer workstations, container hosts, and environments where untrusted or low-privileged local users can run code.

Exploitation context

The CVE record gives AV:L/PR:L/UI:N, meaning exploitation requires local privileges but no user interaction. The bundle does not state active exploitation, and KEV is false. No public exploit status is established by the provided sources.

Researcher notes

The source evidence supports a local kernel slab out-of-bounds write caused by seq_file overflow accounting in statmount_mnt_idmap(). The exact affected downstream distribution packages are not provided, so validation should rely on vendor backport status, not only upstream version strings.

Mitigation direction

  • Check vendor kernel advisories for affected distribution packages.
  • Prioritize kernel updates containing the referenced stable fixes.
  • Restrict local shell access on shared systems until remediated.
  • Reduce exposure from untrusted containers and low-privileged local users.
  • Track distro backports, because fixed package versions may differ from upstream versions.

Validation and detection

  • Inventory Linux kernel versions across servers, workstations, and container hosts.
  • Compare running kernels against vendor advisories and the CVE affected-version record.
  • Confirm installed kernels include the referenced upstream stable commits or vendor backports.
  • Review multi-user and container-host systems first due to local-privilege prerequisites.
  • Monitor CVE and vendor pages for corrected version ranges or exploitation updates.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-64074 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-64074Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux37c4a9590e1efcae7749682239fc22a330d2d325, 37c4a9590e1efcae7749682239fc22a330d2d325, 37c4a9590e1efcae7749682239fc22a330d2d325unaffected
LinuxLinux6.15, 0, 6.18.34, 7.0.11, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.