LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23249: xfs: check for deleted cursors when revalidating two btrees

In the Linux kernel, the following vulnerability has been resolved: xfs: check for deleted cursors when revalidating two btrees The free space and inode btree repair functions will rebuild both btrees at the same time, after which it needs to evaluate both btrees to confirm that the corruptions are gone. However, Jiaming Zhang ran syzbot and produced a crash in the second xchk_allocbt call. His root-cause analysis is as follows (with minor corrections): In xrep_revalidate_allocbt(), xchk_allocbt() is called twice (first for BNOBT, second for CNTBT). The cause of this issue is that the first call nullified the cursor required by the second call. Let's first enter xrep_revalidate_allocbt() via following call chain: xfs_file_ioctl() -> xfs_ioc_scrubv_metadata() -> xfs_scrub_metadata() -> `sc->ops->repair_eval(sc)` -> xrep_revalidate_allocbt() xchk_allocbt() is called twice in this function. In the first call: /* Note that sc->sm->sm_type is XFS_SCRUB_TYPE_BNOPT now */ xchk_allocbt() -> xchk_btree() -> `bs->scrub_rec(bs, recp)` -> xchk_allocbt_rec() -> xchk_allocbt_xref() -> xchk_allocbt_xref_other() since sm_type is XFS_SCRUB_TYPE_BNOBT, pur is set to &sc->sa.cnt_cur. Kernel called xfs_alloc_get_rec() and returned -EFSCORRUPTED. Call chain: xfs_alloc_get_rec() -> xfs_btree_get_rec() -> xfs_btree_check_block() -> (XFS_IS_CORRUPT || XFS_TEST_ERROR), the former is false and the latter is true, return -EFSCORRUPTED. This should be caused by ioctl$XFS_IOC_ERROR_INJECTION I guess. Back to xchk_allocbt_xref_other(), after receiving -EFSCORRUPTED from xfs_alloc_get_rec(), kernel called xchk_should_check_xref(). In this function, *curpp (points to sc->sa.cnt_cur) is nullified. Back to xrep_revalidate_allocbt(), since sc->sa.cnt_cur has been nullified, it then triggered null-ptr-deref via xchk_allocbt() (second call) -> xchk_btree(). So. The bnobt revalidation failed on a cross-reference attempt, so we deleted the cntbt cursor, and then crashed when we tried to revalidate the cntbt. Therefore, check for a null cntbt cursor before that revalidation, and mark the repair incomplete. Also we can ignore the second tree entirely if the first tree was rebuilt but is already corrupt. Apply the same fix to xrep_revalidate_iallocbt because it has the same problem.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel XFS filesystem bug that can crash the kernel during metadata scrub/repair revalidation. The source describes a null pointer dereference after one repair check deletes a cursor needed by the next check. Evidence points to reliability and denial-of-service risk, not data theft or remote compromise.

Executive priority

Treat as a stability risk for Linux systems using XFS, especially storage-sensitive servers. Patch through normal kernel maintenance unless the environment heavily uses XFS scrub/repair, in which case prioritize faster validation and rollout.

Technical view

The flaw is in XFS repair revalidation for allocation and inode btrees. When the first btree cross-reference fails, shared scrub state can nullify the second btree cursor. The next xchk_allocbt or iallocbt pass can dereference that null cursor. Kernel stable commits add null-cursor checks and mark repair incomplete.

Likely exposure

Systems running affected Linux kernels with XFS filesystems are the relevant exposure. Risk is most relevant where XFS online scrub or repair ioctls can be invoked. The source bundle does not establish remote reachability or default exploitability.

Exploitation context

No active exploitation is cited, and KEV is false. The reported crash came from syzbot testing, with discussion of error injection as a possible trigger. Public sources provided do not show a weaponized exploit or real-world attacks.

Researcher notes

The record lacks CVSS, CWE, and detailed vendor package ranges. The affected version data is commit and kernel-range oriented, so validate against upstream stable commits and downstream backports. Avoid assuming remote exploitability from the provided evidence.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Check distribution kernel advisories for the matching backport.
  • Restrict XFS scrub/repair access on unpatched systems where feasible.
  • Prioritize hosts using XFS for critical storage workloads.
  • Monitor for kernel oops or panic events in XFS scrub paths.

Validation and detection

  • Inventory Linux kernel versions across XFS hosts.
  • Confirm whether referenced stable commits or vendor backports are present.
  • Identify systems exposing XFS scrub or repair operational workflows.
  • Review logs for XFS scrub, null pointer dereference, oops, or panic events.
  • Track vendor advisories until exact affected package ranges are confirmed.
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-23249 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
LinuxLinuxdbfbf3bdf639a20da7d5fb390cd2e197d25aa418, dbfbf3bdf639a20da7d5fb390cd2e197d25aa418, dbfbf3bdf639a20da7d5fb390cd2e197d25aa418, dbfbf3bdf639a20da7d5fb390cd2e197d25aa418unaffected
LinuxLinux6.8, 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.