Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-22121: ext4: fix out-of-bound read in ext4_xattr_inode_dec_ref_all()

Noroxi assessment

Priority: Monitor (action score 28/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.21% (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 098927a13fd918bd7c64c2de905350a1ad7b4a3a, 0c8fbb6ffb3c8f5164572ca88e4ccb6cd6a41ca8, 27202452b0bc942fdc3db72a44c4dcdab96d5b56; azl3 kernel 6.6.121.1-1 on Azure Linux 3.0 6.6.121.1-1.

Low priority for now. Upgrade to Linux Linux 098927a13fd918bd7c64c2de905350a1ad7b4a3a, 0c8fbb6ffb3c8f5164572ca88e4ccb6cd6a41ca8, 27202452b0bc942fdc3db72a44c4dcdab96d5b56; azl3 kernel 6.6.121.1-1 on Azure Linux 3.0 6.6.121.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: fix out-of-bound read in ext4_xattr_inode_dec_ref_all() There's issue as follows: BUG: KASAN: use-after-free in ext4_xattr_inode_dec_ref_all+0x6ff/0x790 Read of size 4 at addr ffff88807b003000 by task syz-executor.0/15172 CPU: 3 PID: 15172 Comm: syz-executor.0 Call Trace: __dump_stack lib/dump_stack.c:82 [inline] dump_stack+0xbe/0xfd lib/dump_stack.c:123 print_address_description.constprop.0+0x1e/0x280 mm/kasan/report.c:400 __kasan_report.cold+0x6c/0x84 mm/kasan/report.c:560 kasan_report+0x3a/0x50 mm/kasan/report.c:585 ext4_xattr_inode_dec_ref_all+0x6ff/0x790 fs/ext4/xattr.c:1137 ext4_xattr_delete_inode+0x4c7/0xda0 fs/ext4/xattr.c:2896 ext4_evict_inode+0xb3b/0x1670 fs/ext4/inode.c:323 evict+0x39f/0x880 fs/inode.c:622 iput_final fs/inode.c:1746 [inline] iput fs/inode.c:1772 [inline] iput+0x525/0x6c0 fs/inode.c:1758 ext4_orphan_cleanup fs/ext4/super.c:3298 [inline] ext4_fill_super+0x8c57/0xba40 fs/ext4/super.c:5300 mount_bdev+0x355/0x410 fs/super.c:1446 legacy_get_tree+0xfe/0x220 fs/fs_context.c:611 vfs_get_tree+0x8d/0x2f0 fs/super.c:1576 do_new_mount fs/namespace.c:2983 [inline] path_mount+0x119a/0x1ad0 fs/namespace.c:3316 do_mount+0xfc/0x110 fs/namespace.c:3329 __do_sys_mount fs/namespace.c:3540 [inline] __se_sys_mount+0x219/0x2e0 fs/namespace.c:3514 do_syscall_64+0x33/0x40 arch/x86/entry/common.c:46 entry_SYSCALL_64_after_hwframe+0x67/0xd1 Memory state around the buggy address: ffff88807b002f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff88807b002f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff88807b003000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff88807b003080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88807b003100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff Above issue happens as ext4_xattr_delete_inode() isn't check xattr is valid if xattr is in inode. To solve above issue call xattr_check_inode() check if xattr if valid in inode. In fact, we can directly verify in ext4_iget_extra_inode(), so that there is no divergent verification.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Apr 16, 2025
Updated
Oct 15, 2026
EPSS
0.2% · 12th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.1
CNA · Linux
8.4
1.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-22121

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 kernel4.13 and later · before 6.14.2

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

    • 4.13affected
    • e50e5129f384ae282adebfb561189cdb19b81cee and later · before 27202452b0bc942fdc3db72a44c4dcdab96d5b56affected · git
    • e50e5129f384ae282adebfb561189cdb19b81cee and later · before b374e9ecc92aaa7fb2ab221ee3ff5451118ab566affected · git
    • e50e5129f384ae282adebfb561189cdb19b81cee and later · before c000a8a9b5343a5ef867df173c6349672dacbd0faffected · git
    • e50e5129f384ae282adebfb561189cdb19b81cee and later · before 3c591353956ffcace2cc74d09930774afed60619affected · git
    • e50e5129f384ae282adebfb561189cdb19b81cee and later · before 098927a13fd918bd7c64c2de905350a1ad7b4a3aaffected · git
    • e50e5129f384ae282adebfb561189cdb19b81cee and later · before 0c8fbb6ffb3c8f5164572ca88e4ccb6cd6a41ca8affected · git
    • e50e5129f384ae282adebfb561189cdb19b81cee and later · before 5701875f9609b000d91351eaa6bfd97fe2f157f4affected · git
    • before 4.13not affected · semver
    • 5.10.248 and later · up to and including 5.10.*not affected · semver

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.24.1.el10_06.12.0-55.24.1.el10_0
AlmaLinux:10kernel-docbefore 6.12.0-55.24.1.el10_06.12.0-55.24.1.el10_0
AlmaLinux:9kernelbefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-64kbefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-64k-corebefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-64k-debugbefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-64k-develbefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-corebefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-cross-headersbefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-debugbefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-debug-corebefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-debug-develbefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-570.30.1.el9_65.14.0-570.30.1.el9_6

+96

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-22115Apr 16, 2025 · btrfs: fix block group refcount race in btrfs_create_pending_block_groups()
    18Monitor
  • ← EarlierCVE-2025-22117Apr 16, 2025 · ice: fix using untrusted value of pkt_len in ice_vc_fdir_parse_raw()
    22Monitor
  • Later →CVE-2025-22124Apr 16, 2025 · md/md-bitmap: fix wrong bitmap_limit for clustermd when write sb
    22Monitor

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 Linux098927a13fd918bd7c64c2de905350a1ad7b4a3aVendor (CNA)
Linux Linux0c8fbb6ffb3c8f5164572ca88e4ccb6cd6a41ca8Vendor (CNA)
Linux Linux27202452b0bc942fdc3db72a44c4dcdab96d5b56Vendor (CNA)
Linux Linux3c591353956ffcace2cc74d09930774afed60619Vendor (CNA)
Linux Linux5701875f9609b000d91351eaa6bfd97fe2f157f4Vendor (CNA)
Linux Linuxb374e9ecc92aaa7fb2ab221ee3ff5451118ab566Vendor (CNA)
Linux Linuxc000a8a9b5343a5ef867df173c6349672dacbd0fVendor (CNA)
azl3 kernel 6.6.121.1-1 on Azure Linux 3.06.6.121.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0—Microsoft (MSRC)
almalinux:kernel5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-570.30.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-abi-stablelists6.12.0-55.24.1.el10_0 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-doc6.12.0-55.24.1.el10_0 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.162-1~deb11u1 · Debian:11Package registry (OSV)
red hat:kernel-rt0:5.14.0-70.138.1.rt21.210.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-core0:5.14.0-70.138.1.rt21.210.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug0:5.14.0-70.138.1.rt21.210.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:5.14.0-70.138.1.rt21.210.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:5.14.0-70.138.1.rt21.210.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:5.14.0-70.138.1.rt21.210.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:5.14.0-70.138.1.rt21.210.el9_0 · Red Hat:rhel_e4s:9.0::nfvPackage registry (OSV)

+6

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
high · data can be read
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
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.

ATT&CK techniques

—

Change log

  1. SSVC exploitation— → none
  2. Fix✗ → ✓

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

References

Show all references (8 more)

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

All records