Skip to main content
VulnerabilityPublished Updated

CVE-2025-38701: Linux kernel · ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr

Affects Linux kernelSource CVE Database V5

0
Compare

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

Data as of 5 Nov 2026, 21:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
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 d960f4b793912f35e9d72bd9d1e90553063fcbf1, 8085a7324d8ec448c4a764af7853e19bbd64e17a, 2817ac83cb4732597bf36853fe13ca616f4ee4e2 +6

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 2025

  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 to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 67cf5b09a46f72e048501b84996f2f77bc42e947, < d960f4b793912f35e9d72bd9d1e90553063fcbf1
Fixed in
  • d960f4b793912f35e9d72bd9d1e90553063fcbf1
LinuxLinuxAffected
  • ≥ 67cf5b09a46f72e048501b84996f2f77bc42e947, < 8085a7324d8ec448c4a764af7853e19bbd64e17a
Fixed in
  • 8085a7324d8ec448c4a764af7853e19bbd64e17a
LinuxLinuxAffected
  • ≥ 67cf5b09a46f72e048501b84996f2f77bc42e947, < 2817ac83cb4732597bf36853fe13ca616f4ee4e2
Fixed in
  • 2817ac83cb4732597bf36853fe13ca616f4ee4e2
LinuxLinuxAffected
  • ≥ 67cf5b09a46f72e048501b84996f2f77bc42e947, < 1199a6399895f4767f0b9a68a6ff47c3f799b7c7
Fixed in
  • 1199a6399895f4767f0b9a68a6ff47c3f799b7c7
LinuxLinuxAffected
  • ≥ 67cf5b09a46f72e048501b84996f2f77bc42e947, < 279c87ef7b9da34f65c2e4db586e730b667a6fb9
Fixed in
  • 279c87ef7b9da34f65c2e4db586e730b667a6fb9
LinuxLinuxAffected
  • ≥ 67cf5b09a46f72e048501b84996f2f77bc42e947, < 099b847ccc6c1ad2f805d13cfbcc83f5b6d4bc42
Fixed in
  • 099b847ccc6c1ad2f805d13cfbcc83f5b6d4bc42

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr A syzbot fuzzed image triggered a BUG_ON in ext4_update_inline_data() when an inode had the INLINE_DATA_FL flag set but was missing the system.data extended attribute. Since this can happen due to a maiciouly fuzzed file system, we shouldn't BUG, but rather, report it as a corrupted file system. Add similar replacements of BUG_ON with EXT4_ERROR_INODE() ii ext4_create_inline_data() and ext4_inline_data_truncate().

References

Community reviews

Loading reviews…