LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22120: ext4: goto right label 'out_mmap_sem' in ext4_setattr()

In the Linux kernel, the following vulnerability has been resolved: ext4: goto right label 'out_mmap_sem' in ext4_setattr() Otherwise, if ext4_inode_attach_jinode() fails, a hung task will happen because filemap_invalidate_unlock() isn't called to unlock mapping->invalidate_lock. Like this: EXT4-fs error (device sda) in ext4_setattr:5557: Out of memory INFO: task fsstress:374 blocked for more than 122 seconds. Not tainted 6.14.0-rc1-next-20250206-xfstests-dirty #726 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:fsstress state:D stack:0 pid:374 tgid:374 ppid:373 task_flags:0x440140 flags:0x00000000 Call Trace: <TASK> __schedule+0x2c9/0x7f0 schedule+0x27/0xa0 schedule_preempt_disabled+0x15/0x30 rwsem_down_read_slowpath+0x278/0x4c0 down_read+0x59/0xb0 page_cache_ra_unbounded+0x65/0x1b0 filemap_get_pages+0x124/0x3e0 filemap_read+0x114/0x3d0 vfs_read+0x297/0x360 ksys_read+0x6c/0xe0 do_syscall_64+0x4b/0x110 entry_SYSCALL_64_after_hwframe+0x76/0x7e

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-22120 is a Linux kernel ext4 bug that can leave a filesystem lock unreleased after an error path. The observed impact is a hung task, which can disrupt workloads using ext4. The supplied sources do not provide CVSS, confirmed exploitation, or a complete operational impact assessment.

Executive priority

Treat this as a reliability and availability issue for Linux/ext4 infrastructure. Prioritize patching in fleets where hung tasks could affect production workloads, but do not escalate as actively exploited based on the supplied evidence.

Technical view

In ext4_setattr(), failure of ext4_inode_attach_jinode() can jump to the wrong cleanup label, skipping filemap_invalidate_unlock() for mapping->invalidate_lock. The kernel fix changes control flow to the out_mmap_sem cleanup path. The source shows hung fsstress activity after an out-of-memory error.

Likely exposure

Exposure is likely limited to Linux systems using ext4 on affected kernel versions. The bundle identifies Linux kernel involvement and lists affected/fixed version data, including 6.6.89, 6.12.26, 6.14.2, and 6.15, but the flattened version status is not fully clear.

Exploitation context

No active exploitation is supported by the provided sources, and KEV is false. The evidence describes a reliability failure under an error path, not remote code execution or privilege escalation. Trigger requirements are not fully documented in the bundle.

Researcher notes

The vulnerable behavior is an incomplete cleanup path in ext4_setattr(). Evidence is limited to the CVE description and kernel stable references. The source bundle does not define attacker prerequisites, CVSS, CWE, or a distribution-specific affected matrix.

Mitigation direction

  • Check your distribution kernel advisory for CVE-2025-22120 package status.
  • Update to a vendor kernel containing the referenced stable ext4 fixes.
  • Prioritize ext4 systems running unpatched 6.13-era or affected stable kernels.
  • Monitor production hosts for repeated hung-task reports involving ext4_setattr().

Validation and detection

  • Inventory Linux kernel versions on ext4-backed systems.
  • Confirm whether the running kernel includes one of the referenced stable commits.
  • Review kernel logs for hung tasks or ext4_setattr out-of-memory errors.
  • Map distribution packages to upstream fixed stable versions before closing exposure.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-22120 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux93011887013dbaa0e3a0285176ca89be153df651, b6ce2dbe984bcd7fb0c1df15b5e2fa57e1574a8e, c7fc0366c65628fd69bfc310affec4918199aae2, c7fc0366c65628fd69bfc310affec4918199aae2, 6.6.70, 6.12.5unaffected
LinuxLinux6.13, 0, 6.6.89, 6.12.26, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.