Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-38220: ext4: only dirty folios when data journaling regular files

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux be5f3061a6f904e3674257879e71881ceee5b673, cf6a4c4ac7b6e3214f25df594c9689a62f1bb456, d7af6eee8cd60f55aa8c5fe2b91f11ec0c9a0f27; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1; azl3 kernel 6.6.96.1-1 on Azure Linux 3.0 6.6.96.1-1.

Low priority for now. Upgrade to Linux Linux be5f3061a6f904e3674257879e71881ceee5b673, cf6a4c4ac7b6e3214f25df594c9689a62f1bb456, d7af6eee8cd60f55aa8c5fe2b91f11ec0c9a0f27; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1; azl3 kernel 6.6.96.1-1 on Azure Linux 3.0 6.6.96.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jul 4, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 6th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-38220

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.4 and later · before 6.6.95
  • linux linux kernel6.7 and later · before 6.12.35
  • linux linux kernel6.13 and later · before 6.15.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.4affected
    • d84c9ebdac1e39bc7b036c0c829ee8c1956edabc and later · before cf6a4c4ac7b6e3214f25df594c9689a62f1bb456affected · git
    • d84c9ebdac1e39bc7b036c0c829ee8c1956edabc and later · before be5f3061a6f904e3674257879e71881ceee5b673affected · git
    • d84c9ebdac1e39bc7b036c0c829ee8c1956edabc and later · before d7af6eee8cd60f55aa8c5fe2b91f11ec0c9a0f27affected · git
    • d84c9ebdac1e39bc7b036c0c829ee8c1956edabc and later · before e26268ff1dcae5662c1b96c35f18cfa6ab73d9deaffected · git
    • before 6.4not affected · semver
    • 6.6.95 and later · up to and including 6.6.*not affected · semver
    • 6.12.35 and later · up to and including 6.12.*not affected · semver
    • 6.15.4 and later · up to and including 6.15.*not affected · semver
    • 6.16 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-55.30.1.el10_06.12.0-55.30.1.el10_0
AlmaLinux:10kernel-docbefore 6.12.0-55.30.1.el10_06.12.0-55.30.1.el10_0
Debian:13linuxbefore 6.12.35-16.12.35-1
Red Hat:enterprise_linux:10.0kernelbefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64kbefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-corebefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debugbefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-corebefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-debuginfobefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-develbefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-devel-matchedbefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-modulesbefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-modules-corebefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-modules-extrabefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debuginfobefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-develbefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-devel-matchedbefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-modulesbefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-modules-corebefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-modules-extrabefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-abi-stablelistsbefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-corebefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-debugbefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0
Red Hat:enterprise_linux:10.0kernel-debug-corebefore 0:6.12.0-55.30.1.el10_00:6.12.0-55.30.1.el10_0

+71

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-38218Jul 4, 2025 · f2fs: fix to do sanity check on sit_bitmap_size
    22Monitor
  • ← EarlierCVE-2025-38219Jul 4, 2025 · f2fs: prevent kernel warning due to negative i_nlink from corrupted image
    22Monitor
  • Later →CVE-2025-38221Jul 4, 2025 · ext4: fix out of bounds punch offset
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linuxbe5f3061a6f904e3674257879e71881ceee5b673Vendor (CNA)
Linux Linuxcf6a4c4ac7b6e3214f25df594c9689a62f1bb456Vendor (CNA)
Linux Linuxd7af6eee8cd60f55aa8c5fe2b91f11ec0c9a0f27Vendor (CNA)
Linux Linuxe26268ff1dcae5662c1b96c35f18cfa6ab73d9deVendor (CNA)
azl3 kernel 6.6.92.2-2 on Azure Linux 3.06.6.96.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.96.1-1 on Azure Linux 3.06.6.96.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel-abi-stablelists6.12.0-55.30.1.el10_0 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-doc6.12.0-55.30.1.el10_0 · AlmaLinux:10Package registry (OSV)
debian:linux6.12.35-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:6.12.0-55.30.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
rocky linux:kernel0:6.12.0-55.30.1.el10_0 · Rocky Linux:10Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-476 · NULL Pointer Dereference

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records