Skip to main content
VulnerabilityPublished Updated

CVE-2026-23223: Linux kernel · xfs: fix UAF in xchk_btree_check_block_owner

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ed82e7949f5cac3058f4100f3cd670531d41a266 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 23:24 UTC

Severity
Unrated

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

  1. Disclosed: evidence found.

    CVE published 18 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ ec793e690f801d97a7ae2a0d429fea1fee4d44aa, < ed82e7949f5cac3058f4100f3cd670531d41a266
Fixed in
  • ed82e7949f5cac3058f4100f3cd670531d41a266
LinuxLinuxAffected
  • ≥ ec793e690f801d97a7ae2a0d429fea1fee4d44aa, < ba5264610423d9653aa36920520902d83841bcfd
Fixed in
  • ba5264610423d9653aa36920520902d83841bcfd
LinuxLinuxAffected
  • ≥ ec793e690f801d97a7ae2a0d429fea1fee4d44aa, < 1d411278dda293a507cb794db7d9ed3511c685c6
Fixed in
  • 1d411278dda293a507cb794db7d9ed3511c685c6
LinuxLinuxAffected
  • ≥ ec793e690f801d97a7ae2a0d429fea1fee4d44aa, < 1c253e11225bc5167217897885b85093e17c2217
Fixed in
  • 1c253e11225bc5167217897885b85093e17c2217
LinuxLinuxAffected
  • =6.9
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

Community reviews

Loading reviews…