🛡️ AZL-64767 — kernel

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

CVE-2025-38220 affecting package kernel for versions less than 6.6.96.1-1

In the Linux kernel, the following vulnerability has been resolved:

ext4: only dirty folios when data journaling regular files

fstest generic/388 occasionally reproduces a crash that looks as

follows:

BUG: kernel NULL pointer dereference, address: 0000000000000000

...

Call Trace:

<TASK>

ext4_block_zero_page_range+0x30c/0x380 [ext4]

ext4_truncate+0x436/0x440 [ext4]

ext4_process_orphan+0x5d/0x110 [ext4]

ext4_orphan_cleanup+0x124/0x4f0 [ext4]

ext4_fill_super+0x262d/0x3110 [ext4]

get_tree_bdev_flags+0x132/0x1d0

vfs_get_tree+0x26/0xd0

vfs_cmd_create+0x59/0xe0

__do_sys_fsconfig+0x4ed/0x6b0

do_syscall_64+0x82/0x170

...

This occurs when processing a symlink inode from the orphan list. The

partial block zeroing code in the truncate path calls

ext4_dirty_journalled_data() -> folio_mark_dirty(). The latter calls

mapping->a_ops->dirty_folio(), but symlink inodes are not assigned an

a_ops vector in ext4, hence the crash.

To avoid this problem, update the ext4_dirty_journalled_data() helper to

only mark the folio dirty on regular files (for which a_ops is

assigned). This also matches the journaling logic in the ext4_symlink()

creation path, where ext4_handle_dirty_metadata() is called directly.

Affected software

AZL-64767 is recorded against 1 package.

  • kernel (fixed in 6.6.96.1-1)

Timeline and source

Published on 4 July 2025 and last revised on 21 April 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

nvd.nist.gov (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2025-07-04
Updated 2026-08-12
Modified 2026-04-21
Fix URL N/A

Affected Packages

Software From version Fixed in
kernel — 6.6.96.1-1

Similar Threats

Free Vulnerability Check

Is your site affected by AZL-64767?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against AZL-64767 and other known CVE records.

Scan My Site Free →

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.