LiveActive security incident?Get immediate response
CVE Record

CVE-2026-31694: fuse: reject oversized dirents in page cache

In the Linux kernel, the following vulnerability has been resolved: fuse: reject oversized dirents in page cache fuse_add_dirent_to_cache() computes a serialized dirent size from the server-controlled namelen field and copies the dirent into a single page-cache page. The existing logic only checks whether the dirent fits in the remaining space of the current page and advances to a fresh page if not. It never checks whether the dirent itself exceeds PAGE_SIZE. As a result, a malicious FUSE server can return a dirent with namelen=4095, producing a serialized record size of 4120 bytes. On 4 KiB page systems this causes memcpy() to overflow the cache page by 24 bytes into the following kernel page. Reject dirents that cannot fit in a single page before copying them into the readdir cache.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A malicious FUSE filesystem server can corrupt Linux kernel memory by returning an oversized directory entry. Successful abuse could compromise confidentiality, integrity, or availability. The attacker must have local, low-privileged access and a path to supply malicious FUSE responses; no user interaction is required.

Executive priority

Treat this as a high-priority kernel update for multi-user systems, shared compute, and environments permitting untrusted FUSE servers. Prioritize exposed systems promptly, then address lower-exposure hosts through normal accelerated patching. Current sources do not support declaring an exploitation emergency.

Technical view

The server-controlled namelen can produce a 4,120-byte serialized directory entry. On 4 KiB-page systems, fuse_add_dirent_to_cache() copies it into one page, overflowing 24 bytes into the next kernel page. The fix rejects directory entries larger than a page before caching them.

Likely exposure

Exposure requires an affected Linux kernel, 4 KiB pages for the documented overflow, and interaction with a malicious FUSE server. Risk is greatest where low-privileged or untrusted users can operate FUSE filesystems. The supplied affected-version data is ambiguous, so package exposure must be confirmed through vendor guidance and fix-commit mapping.

Exploitation context

The CVSS vector describes local, low-complexity exploitation requiring low privileges and no user interaction, with potentially high confidentiality, integrity, and availability impact. The source bundle marks KEV false and provides no evidence of active exploitation, public proof-of-concept code, or confirmed weaponization.

Researcher notes

The boundary error occurs because remaining-page capacity is checked without first proving the complete record fits within one page. The documented case uses namelen 4095 and a 4 KiB page. Source metadata lists inconsistent-looking affected versions and repeated commit identifiers; researchers should rely on code ancestry and vendor package mappings rather than version strings alone.

Mitigation direction

  • Apply a vendor-supported kernel update containing the applicable cited stable fix.
  • Follow distribution guidance to map the cited fix commits to packaged kernel versions.
  • Until updated, restrict unnecessary FUSE access and prevent untrusted users from supplying FUSE servers.
  • Reboot systems after updating so the fixed kernel is running.

Validation and detection

  • Inventory running kernel versions, page sizes, and systems permitting FUSE use.
  • Map each running kernel package against vendor advisories and the cited stable fix commits.
  • Confirm the fixed kernel is active after reboot, not merely installed.
  • Review whether untrusted or low-privileged users can operate FUSE servers.
  • Use controlled regression testing to confirm oversized directory entries are rejected safely.
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-31694 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-31694Attack 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
LinuxLinux27992ef80770d61a57f6c3a551735b08cefdffa3, 27992ef80770d61a57f6c3a551735b08cefdffa3, 27992ef80770d61a57f6c3a551735b08cefdffa3unaffected
LinuxLinux6.15, 0, 6.18.25, 7.0.2, 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.