CVE-2022-50730: linux

CVSS: UnknownDeferred
AliasesUBUNTU-CVE-2022-50730DEBIAN-CVE-2022-50730
Published 24-12-2025Last modified 11-05-2026
Open JSON

Vulnerability summary

CVE-2022-50730 is a vulnerability in linux with no CVSS score yet. EPSS estimates a 0.24% chance of exploitation in the next 30 days, higher than 14.7% of scored vulnerabilities.

Overall risk
0/100
0100
Minimal · default modelHow is this calculated?
CVSS score
Not scored
010
No CVSS score recorded
EPSS score
0.24%
0%100%
Low · 0.00 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 9 · Related 7
RHSA-2023:2458RHSA-2024:3138SUSE-SU-2026:0263-1SUSE-SU-2026:0316-1SUSE-SU-2026:0317-1SUSE-SU-2026:0350-1

Timeline

  1. 24-12-2025
    PublishedVulnerability first disclosed.
  2. 11-05-2026
    Last modifiedVulnerability information updated.

Description

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

CVSS metrics

Risk metrics not yet published.

EPSS trend

Probability

0.24%

Chance of exploitation in the next 30 days

Percentile

15%

Versus all other CVEs

30-day change

0.00 pp

From 0.24% on 21-09-2026

21-09-202621-10-2026
EPSS score
0.24%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Ubuntu104 products
  • linux< 5.15.0-69.76
  • linux-allwinner-5.19All versions (No fix recorded)
  • linux-aws< 5.15.0-1033.37
  • linux-aws-5.0All versions (No fix recorded)
  • linux-aws-5.11All versions (No fix recorded)
Debian1 product
  • linux< 6.1.4-1
Linux1 product
  • linux≥ ceff86fddae8748fe00d4f2d249cb02cae62ad84, < bdc698ce91f232fd5eb11d2373e9f82f687314b8 | ≥ ceff86fddae8748fe00d4f2d249cb02cae62ad84, < 0d041b7251c13679a0f6c7926751ce1d8a7237c1 | ≥ ceff86fddae8748fe00d4f2d249cb02cae62ad84, < 3b893cc9a8d8b4e486a6639f5e107b56b7197d2e | ≥ ceff86fddae8748fe00d4f2d249cb02cae62ad84, < b085fb43feede48ebf80ab7e2dd150c8d9902932 | ≥ ceff86fddae8748fe00d4f2d249cb02cae62ad84, < bc12ac98ea2e1b70adc6478c8b473a0003b659d3 | 5.8

3 vendors · 106 products

References

8 links