CVE-2026-23223: Linux kernel · xfs: fix UAF in xchk_btree_check_block_owner
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ed82e7949f5cac3058f4100f3cd670531d41a266 : update Linux kernel when convenient.
Data as of 5 Nov 2026, 23:24 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in ed82e7949f5cac3058f4100f3cd670531d41a266, ba5264610423d9653aa36920520902d83841bcfd, 1d411278dda293a507cb794db7d9ed3511c685c6 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade Linux kernel to ed82e7949f5cac3058f4100f3cd670531d41a266, ba5264610423d9653aa36920520902d83841bcfd, 1d411278dda293a507cb794db7d9ed3511c685c6 or 1c253e11225bc5167217897885b85093e17c2217.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: xfs: fix UAF in xchk_btree_check_block_owner We cannot dereference bs->cur when trying to determine if bs->cur aliases bs->sc->sa.{bno,rmap}_cur after the latter has been freed. Fix this by sampling before type before any freeing could happen. The correct temporal ordering was broken when we removed xfs_btnum_t.
References
- git.kernel.org/stable/c/1d411278dda293a507cb794db7d9ed3511c685c6 (opens in a new tab)
- git.kernel.org/stable/c/ed82e7949f5cac3058f4100f3cd670531d41a266 (opens in a new tab)
- git.kernel.org/stable/c/ba5264610423d9653aa36920520902d83841bcfd (opens in a new tab)
- git.kernel.org/stable/c/1c253e11225bc5167217897885b85093e17c2217 (opens in a new tab)