LiveActive security incident?Get immediate response
CVE Record

CVE-2026-31709: smb: client: validate the whole DACL before rewriting it in cifsacl

In the Linux kernel, the following vulnerability has been resolved: smb: client: validate the whole DACL before rewriting it in cifsacl build_sec_desc() and id_mode_to_cifs_acl() derive a DACL pointer from a server-supplied dacloffset and then use the incoming ACL to rebuild the chmod/chown security descriptor. The original fix only checked that the struct smb_acl header fits before reading dacl_ptr->size or dacl_ptr->num_aces. That avoids the immediate header-field OOB read, but the rewrite helpers still walk ACEs based on pdacl->num_aces with no structural validation of the incoming DACL body. A malicious server can return a truncated DACL that still contains a header, claims one or more ACEs, and then drive replace_sids_and_copy_aces() or set_chmod_dacl() past the validated extent while they compare or copy attacker-controlled ACEs. Factor the DACL structural checks into validate_dacl(), extend them to validate each ACE against the DACL bounds, and use the shared validator before the chmod/chown rebuild paths. parse_dacl() reuses the same validator so the read-side parser and write-side rewrite paths agree on what constitutes a well-formed incoming DACL.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-31709 is a Linux kernel SMB client flaw. A malicious or compromised SMB server can send malformed access-control data that the client mishandles while rebuilding permissions. The stated impact is high for confidentiality, integrity, and availability, but user interaction is required because a client must interact with the server.

Executive priority

Treat this as a high-priority kernel update for Linux fleets that use SMB shares. It is not shown as actively exploited in the supplied sources, but the potential impact is severe if clients connect to hostile SMB infrastructure.

Technical view

The SMB client cifsacl paths derive a DACL from a server-supplied offset. Earlier checks covered only the ACL header, while rewrite helpers still walked ACEs based on unvalidated counts. A truncated DACL could drive out-of-bounds ACE comparison or copying. The fix centralizes DACL validation and checks each ACE against DACL bounds.

Likely exposure

Linux systems using the kernel SMB/CIFS client are the relevant exposure, especially clients mounting SMB shares where ACL rewrite paths such as chmod or chown may process server-supplied DACLs. Exact package exposure should be checked against kernel stable fixes and Linux distribution advisories.

Exploitation context

The provided sources do not show active exploitation, and KEV is false. The scenario requires a malicious or compromised SMB server returning malformed DACL data to a Linux SMB client. No public exploit details are cited in the supplied bundle.

Researcher notes

Key issue is incomplete structural validation of incoming DACL bodies before cifsacl rewrite operations. The fix introduces validate_dacl(), validates each ACE against DACL bounds, and aligns parse and rewrite-side validation. Evidence in the bundle does not include exploit availability or root-cause details beyond the kernel advisory text.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable SMB client fixes.
  • Prioritize Linux clients that mount SMB/CIFS shares from less trusted networks.
  • Restrict SMB/CIFS access to trusted servers where operationally possible.
  • Review Red Hat or distribution advisories for package-specific remediation.
  • Monitor vendor guidance if a fixed package is not yet available.

Validation and detection

  • Inventory Linux hosts using SMB/CIFS mounts or ACL-enabled share workflows.
  • Compare running kernel packages with distribution advisories for CVE-2026-31709.
  • Confirm whether SMB mounts can reach untrusted or user-controlled servers.
  • Check change records for kernel updates containing the listed stable commits.
  • Review exposure of chmod or chown workflows over CIFS-mounted paths.
Prepared
Confidence
high
Sources
12

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.

cwe · low confidence lookup

CWE-1288: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-31709 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
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.

2CVSS vectors
5Timeline events
1ADP providers
20Source links

CVSS vector scores

2 official scores

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
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Linux
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. ADP timelineredhat-SADP

    Reported to Red Hat.

  3. ADP timelineredhat-SADP

    Made public.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

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

ADP provider summaries

redhat-SADPkernel: smb: client: validate the whole DACL before rewriting it in cifsacl
other:Red Hat severity ratingcvssV3_1
  • 2026-05-01T00:00:00.000Z: Reported to Red Hat.
  • 2026-05-01T00:00:00.000Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxbc3e9dd9d104ca1b75644eab87b38ce8a924aef4, bc3e9dd9d104ca1b75644eab87b38ce8a924aef4, bc3e9dd9d104ca1b75644eab87b38ce8a924aef4, bc3e9dd9d104ca1b75644eab87b38ce8a924aef4, bc3e9dd9d104ca1b75644eab87b38ce8a924aef4, bc3e9dd9d104ca1b75644eab87b38ce8a924aef4, bc3e9dd9d104ca1b75644eab87b38ce8a924aef4unaffected
LinuxLinux5.12, 0, 5.15.210, 6.1.176, 6.6.140, 6.12.86, 6.18.35, 7.0.2, 7.1affected
Weakness

CWE details

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

CWE-1288 · source CWE mapping

Improper Validation of Consistency within Input

Improper Validation of Consistency within Input represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.