CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-31694 remediation guide

Linux Linux, linux kernel

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 Ki...

Open CVE record
ProductLinux Linux, linux kernel
Affected versions27992ef80770d61a57f6c3a551735b08cefdffa3, 6.15, >= 4.20 < 6.6.136, >= 6.7 < 6.12.84, >= 6.13 < 6.18.25, >= 6.19 < 7.0.2, 7.1
Fixed versions6.6.136, 6.12.84, 6.18.25, 7.0.2
Priority basisReview · CVSS 7.8 · EPSS 0.28%
01

Identify the affected asset

Confirm whether Linux Linux, linux kernel is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: 27992ef80770d61a57f6c3a551735b08cefdffa3, 6.15, >= 4.20 < 6.6.136, >= 6.7 < 6.12.84, >= 6.13 < 6.18.25, >= 6.19 < 7.0.2, 7.1. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 6.6.136, 6.12.84, 6.18.25, 7.0.2. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.