LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50730: ext4: silence the warning when evicting inode with dioread_nolock

In the Linux kernel, the following vulnerability has been resolved: ext4: silence the warning when evicting inode with dioread_nolock When evicting an inode with default dioread_nolock, it could be raced by the unwritten extents converting kworker after writeback some new allocated dirty blocks. It convert unwritten extents to written, the extents could be merged to upper level and free extent blocks, so it could mark the inode dirty again even this inode has been marked I_FREEING. But the inode->i_io_list check and warning in ext4_evict_inode() missing this corner case. Fortunately, ext4_evict_inode() will wait all extents converting finished before this check, so it will not lead to inode use-after-free problem, every thing is OK besides this warning. The WARN_ON_ONCE was originally designed for finding inode use-after-free issues in advance, but if we add current dioread_nolock case in, it will become not quite useful, so fix this warning by just remove this check. ====== WARNING: CPU: 7 PID: 1092 at fs/ext4/inode.c:227 ext4_evict_inode+0x875/0xc60 ... RIP: 0010:ext4_evict_inode+0x875/0xc60 ... Call Trace: <TASK> evict+0x11c/0x2b0 iput+0x236/0x3a0 do_unlinkat+0x1b4/0x490 __x64_sys_unlinkat+0x4c/0xb0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x46/0xb0 RIP: 0033:0x7fa933c1115b ====== rm kworker ext4_end_io_end() vfs_unlink() ext4_unlink() ext4_convert_unwritten_io_end_vec() ext4_convert_unwritten_extents() ext4_map_blocks() ext4_ext_map_blocks() ext4_ext_try_to_merge_up() __mark_inode_dirty() check !I_FREEING locked_inode_to_wb_and_lock_list() iput() iput_final() evict() ext4_evict_inode() truncate_inode_pages_final() //wait release io_end inode_io_list_move_locked() ext4_release_io_end() trigger WARN_ON_ONCE()

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50730 is a Linux kernel ext4 issue that can trigger a kernel warning during a race while deleting an inode. The upstream description says it does not lead to inode use-after-free and is essentially a false warning condition. Business urgency is low unless warning-induced monitoring noise or kernel panic policies affect operations.

Executive priority

Low priority for emergency response. Address through normal kernel maintenance unless affected systems show repeated warnings, operational instability, or policies that treat kernel warnings as outages.

Technical view

In ext4 with default dioread_nolock behavior, unwritten extent conversion can race inode eviction and mark the inode dirty after I_FREEING. ext4_evict_inode() then hits a WARN_ON_ONCE check. The CVE text states ext4 waits for extent conversion and the issue does not cause inode use-after-free; the fix removes the warning check.

Likely exposure

Exposure is limited to Linux systems using affected kernel builds with ext4. The source lists Linux kernel version entries and stable kernel commits, but exact distribution package ranges are not provided. Systems not using ext4, or already carrying the referenced stable fixes, are less likely to be affected.

Exploitation context

No active exploitation is indicated. The CVE is not in KEV, and the provided sources describe a race causing a warning, not a weaponized privilege escalation or data exposure path. Practical impact appears operational rather than attacker-driven based on current evidence.

Researcher notes

The CVE text is unusually clear that the suspected use-after-free does not occur. The security significance is therefore limited. Version-range detail is incomplete in the provided data, so distro-specific validation is necessary before declaring exposure or closure.

Mitigation direction

  • Apply a vendor kernel update that includes the referenced upstream stable fixes.
  • Prioritize systems using ext4 for write-heavy workloads.
  • Check Linux distribution advisories for exact affected and fixed package versions.
  • If immediate patching is delayed, monitor for repeated ext4_evict_inode warnings.

Validation and detection

  • Inventory Linux kernel versions and identify systems using ext4 filesystems.
  • Compare running kernels against vendor advisories and referenced stable commits.
  • Review kernel logs for WARN_ON_ONCE entries in ext4_evict_inode.
  • Confirm patched systems boot a kernel containing the relevant ext4 fix.
Prepared
Confidence
high
Sources
7

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-2022-50730 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
0Timeline events
0ADP providers
6Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxceff86fddae8748fe00d4f2d249cb02cae62ad84, ceff86fddae8748fe00d4f2d249cb02cae62ad84, ceff86fddae8748fe00d4f2d249cb02cae62ad84, ceff86fddae8748fe00d4f2d249cb02cae62ad84, ceff86fddae8748fe00d4f2d249cb02cae62ad84unaffected
LinuxLinux5.8, 0, 5.10.163, 5.15.87, 6.0.18, 6.1.4, 6.2affected
Weakness

CWE details

No CWE listed

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