LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23251: xfs: only call xf{array,blob}_destroy if we have a valid pointer

In the Linux kernel, the following vulnerability has been resolved: xfs: only call xf{array,blob}_destroy if we have a valid pointer Only call the xfarray and xfblob destructor if we have a valid pointer, and be sure to null out that pointer afterwards. Note that this patch fixes a large number of commits, most of which were merged between 6.9 and 6.10.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-23251 is a Linux kernel XFS filesystem bug where cleanup code could call destructors on invalid pointers. Public sources say the issue is resolved, but they do not state the practical impact, severity, or attacker requirements. Treat affected XFS hosts as needing kernel vendor review rather than emergency action based on current evidence.

Executive priority

Set priority to monitored remediation. Move faster for production storage, multi-tenant platforms, or systems where untrusted users can influence filesystem operations. Current public evidence does not justify claiming active exploitation or critical business urgency.

Technical view

The fix changes XFS code to call xfarray and xfblob destructors only when a valid pointer exists, then nulls the pointer afterward. The CVE notes the patch fixes many commits mostly merged between Linux 6.9 and 6.10. No CVSS, CWE, trigger conditions, or exploitability details are provided in the source bundle.

Likely exposure

Exposure is most plausible on Linux systems running affected kernel versions with XFS functionality present or in use. The source lists Linux kernel versions including 6.10, 6.12.75, 6.18.16, 6.19.6, and 7.0 as affected, but distro-specific package status is not provided.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not marked KEV. They also do not describe a remote attack path, local privilege requirement, filesystem image requirement, or denial-of-service behavior. Any exploitation assessment beyond pointer cleanup risk would be speculative.

Researcher notes

Key gaps remain: no CVSS, CWE, crash description, privilege boundary, reproducer, or distro advisory evidence in the supplied sources. The safest source-grounded position is that this is an upstream Linux XFS memory-safety cleanup fixed by stable commits, with impact still unspecified publicly.

Mitigation direction

  • Check Linux kernel vendor advisories for CVE-2026-23251 package status.
  • Update affected kernels to vendor-supported builds containing the referenced XFS fixes.
  • Prioritize systems using XFS for critical, shared, or multi-tenant storage.
  • Track distro backports instead of relying only on upstream version numbers.

Validation and detection

  • Inventory kernel versions across Linux hosts and containers with host kernel dependency.
  • Identify systems using XFS mounts or XFS-related maintenance workflows.
  • Compare installed kernel packages against vendor advisories for the referenced stable commits.
  • Confirm CVE-2026-23251 is resolved in vulnerability management after patching.
Prepared
Confidence
medium
Sources
6

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-23251 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
5Source 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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxab97f4b1c030750f2475bf4da8a9554d02206640, ab97f4b1c030750f2475bf4da8a9554d02206640, ab97f4b1c030750f2475bf4da8a9554d02206640, ab97f4b1c030750f2475bf4da8a9554d02206640unaffected
LinuxLinux6.10, 0, 6.12.75, 6.18.16, 6.19.6, 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.