LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23282: smb: client: fix oops due to uninitialised var in smb2_unlink()

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix oops due to uninitialised var in smb2_unlink() If SMB2_open_init() or SMB2_close_init() fails (e.g. reconnect), the iovs set @rqst will be left uninitialised, hence calling SMB2_open_free(), SMB2_close_free() or smb2_set_related() on them will oops. Fix this by initialising @close_iov and @open_iov before setting them in @rqst.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash the SMB client path when a file delete operation hits certain initialization failures, such as during reconnect. The public record describes a kernel oops, so the clearest business impact is potential host instability or service disruption on affected Linux systems using SMB client mounts.

Executive priority

Prioritize normal patch management, elevated for Linux systems that depend on SMB shares for production workflows. Current evidence supports an availability concern, but not confirmed active exploitation or a quantified severity score.

Technical view

In smb2_unlink(), failure of SMB2_open_init() or SMB2_close_init() can leave iovec request state uninitialized. Later cleanup or related-request handling may operate on that uninitialized state and trigger an oops. The documented fix initializes close_iov and open_iov before assigning them into rqst.

Likely exposure

Likely exposure is Linux systems running affected kernel builds that use the SMB client/CIFS functionality, especially where SMB reconnect or error paths occur during unlink operations. The source data does not identify specific distributions, configurations, or package versions.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, public exploit code, or attacker requirements. It documents an error-path kernel oops condition. Treat exploitation feasibility as unproven from the provided evidence.

Researcher notes

The record is sparse: no CVSS, CWE, exploit status, or distribution mapping is provided. Analysis should focus on the SMB client unlink error path and whether downstream kernels contain one of the stable commits or equivalent backports.

Mitigation direction

  • Apply kernel or distribution updates containing the referenced stable fixes.
  • Prioritize systems that mount or rely on SMB/CIFS shares.
  • Check vendor advisories for exact fixed package versions.
  • Reduce unnecessary SMB client exposure until patched.
  • Schedule reboots where kernel updates require activation.

Validation and detection

  • Inventory Linux kernel versions across servers and endpoints.
  • Identify hosts using SMB/CIFS client mounts.
  • Confirm the running kernel includes a referenced stable fix.
  • Review kernel logs for SMB client oops events.
  • Validate distribution packages against vendor fixed-version guidance.
Prepared
Confidence
medium
Sources
5

Public sources used

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-23282 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1cf9f2a6a544288516a7b9e883a48eba6246bcf2, 1cf9f2a6a544288516a7b9e883a48eba6246bcf2, 1cf9f2a6a544288516a7b9e883a48eba6246bcf2unaffected
LinuxLinux6.17, 0, 6.18.17, 6.19.7, 7.0affected
Weakness

CWE details

No CWE listed

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