🛡️ CVE-2026-23249 — kernel

🟡 CVSS 5.5 — Medium ✅ No Known Exploit NVD
5.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.

Affected software

CVE-2026-23249 is recorded against 2 packages.

  • kernel (from 6.19.0 up to 6.19.6)
  • linux-kernel (from 6.19 up to 6.19.6)

Timeline and source

Published on 18 March 2026 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

CVE-2026-23249 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity Medium
CVSS Score 5.5
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2026-03-18
Updated 2026-08-20
Modified 2026-08-12

Affected Packages

Software From version Fixed in
kernel 6.19.0 6.19.6
linux-kernel 6.19 6.19.6

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in kernel

CVE-2026-23249 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026