Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/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.24% (FIRST EPSS).
  • Fixed version: Linux Linux 0d041b7251c13679a0f6c7926751ce1d8a7237c1, 3b893cc9a8d8b4e486a6639f5e107b56b7197d2e, b085fb43feede48ebf80ab7e2dd150c8d9902932.

Low priority for now. Upgrade to Linux Linux 0d041b7251c13679a0f6c7926751ce1d8a7237c1, 3b893cc9a8d8b4e486a6639f5e107b56b7197d2e, b085fb43feede48ebf80ab7e2dd150c8d9902932 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: 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()

—No exploit Fix available
Published
Dec 24, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 15th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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-2022-50730

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.

—

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

    • 5.8affected
    • ceff86fddae8748fe00d4f2d249cb02cae62ad84 and later · before bdc698ce91f232fd5eb11d2373e9f82f687314b8affected · git
    • ceff86fddae8748fe00d4f2d249cb02cae62ad84 and later · before 0d041b7251c13679a0f6c7926751ce1d8a7237c1affected · git
    • ceff86fddae8748fe00d4f2d249cb02cae62ad84 and later · before 3b893cc9a8d8b4e486a6639f5e107b56b7197d2eaffected · git
    • ceff86fddae8748fe00d4f2d249cb02cae62ad84 and later · before b085fb43feede48ebf80ab7e2dd150c8d9902932affected · git
    • ceff86fddae8748fe00d4f2d249cb02cae62ad84 and later · before bc12ac98ea2e1b70adc6478c8b473a0003b659d3affected · git
    • before 5.8not affected · semver
    • 5.10.163 and later · up to and including 5.10.*not affected · semver
    • 5.15.87 and later · up to and including 5.15.*not affected · semver
    • 6.0.18 and later · up to and including 6.0.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.4-16.1.4-1
SUSE:Linux Enterprise Micro 5.2kernel-defaultbefore 5.3.18-150300.59.232.15.3.18-150300.59.232.1
SUSE:Linux Enterprise Micro 5.2kernel-default-basebefore 5.3.18-150300.59.232.1.150300.18.138.15.3.18-150300.59.232.1.150300.18.138.1
SUSE:Linux Enterprise Micro 5.2kernel-rtbefore 5.3.18-150300.232.15.3.18-150300.232.1
SUSE:Linux Enterprise Micro 5.2kernel-source-rtbefore 5.3.18-150300.232.15.3.18-150300.232.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2022-50728Dec 24, 2025 · s390/lcs: Fix return type of lcs_start_xmit()
    0Monitor
  • ← EarlierCVE-2022-50729Dec 24, 2025 · ksmbd: Fix resource leak in ksmbd_session_rpc_open()
    0Monitor
  • Later →CVE-2022-50731Dec 24, 2025 · crypto: akcipher - default implementation for setting a private key
    0Monitor

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 Linux0d041b7251c13679a0f6c7926751ce1d8a7237c1Vendor (CNA)
Linux Linux3b893cc9a8d8b4e486a6639f5e107b56b7197d2eVendor (CNA)
Linux Linuxb085fb43feede48ebf80ab7e2dd150c8d9902932Vendor (CNA)
Linux Linuxbc12ac98ea2e1b70adc6478c8b473a0003b659d3Vendor (CNA)
Linux Linuxbdc698ce91f232fd5eb11d2373e9f82f687314b8Vendor (CNA)
debian:linux6.1.4-1 · Debian:12Package registry (OSV)
suse:kernel-default5.3.18-150300.59.232.1 · SUSE:Linux Enterprise Micro 5.2Package registry (OSV)
suse:kernel-default-base5.3.18-150300.59.232.1.150300.18.138.1 · SUSE:Linux Enterprise Micro 5.2Package registry (OSV)
suse:kernel-rt5.3.18-150300.232.1 · SUSE:Linux Enterprise Micro 5.2Package registry (OSV)
suse:kernel-source-rt5.3.18-150300.232.1 · SUSE:Linux Enterprise Micro 5.2Package 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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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 (4 more)

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

All records