{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50730 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50730 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-50730 and fix it if it is affected.\n\nWhat it is: CVE-2022-50730 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-50730 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-50730/ (Markdown: https://insights.sbomify.com/CVE-2022-50730/index.md)","id":"CVE-2022-50730","markdown":"https://insights.sbomify.com/CVE-2022-50730/index.md","name":"CVE-2022-50730","record":{"aliases":["DEBIAN-CVE-2022-50730","GHSA-m98r-2fg7-rppv","UBUNTU-CVE-2022-50730"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel ext4 filesystem triggers a kernel warning during inode eviction, potentially causing a denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\next4: silence the warning when evicting inode with dioread_nolock\n\nWhen evicting an inode with default dioread_nolock, it could be raced by\nthe unwritten extents converting kworker after writeback some new\nallocated dirty blocks. It convert unwritten extents to written, the\nextents could be merged to upper level and free extent blocks, so it\ncould mark the inode dirty again even this inode has been marked\nI_FREEING. But the inode-\u003ei_io_list check and warning in\next4_evict_inode() missing this corner case. Fortunately,\next4_evict_inode() will wait all extents converting finished before this\ncheck, so it will not lead to inode use-after-free problem, every thing\nis OK besides this warning. The WARN_ON_ONCE was originally designed\nfor finding inode use-after-free issues in advance, but if we add\ncurrent dioread_nolock case in, it will become not quite useful, so fix\nthis warning by just remove this check.\n\n ======\n WARNING: CPU: 7 PID: 1092 at fs/ext4/inode.c:227\n ext4_evict_inode+0x875/0xc60\n ...\n RIP: 0010:ext4_evict_inode+0x875/0xc60\n ...\n Call Trace:\n  \u003cTASK\u003e\n  evict+0x11c/0x2b0\n  iput+0x236/0x3a0\n  do_unlinkat+0x1b4/0x490\n  __x64_sys_unlinkat+0x4c/0xb0\n  do_syscall_64+0x3b/0x90\n  entry_SYSCALL_64_after_hwframe+0x46/0xb0\n RIP: 0033:0x7fa933c1115b\n ======\n\nrm                          kworker\n                            ext4_end_io_end()\nvfs_unlink()\n ext4_unlink()\n                             ext4_convert_unwritten_io_end_vec()\n                              ext4_convert_unwritten_extents()\n                               ext4_map_blocks()\n                                ext4_ext_map_blocks()\n                                 ext4_ext_try_to_merge_up()\n                                  __mark_inode_dirty()\n                                   check !I_FREEING\n                                   locked_inode_to_wb_and_lock_list()\n iput()\n  iput_final()\n   evict()\n    ext4_evict_inode()\n     truncate_inode_pages_final() //wait release io_end\n                                    inode_io_list_move_locked()\n                             ext4_release_io_end()\n     trigger WARN_ON_ONCE()","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ext4: silence the warning when evicting inode with dioread_nolock","id":"CVE-2022-50730","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2022"},"n_packages":0,"n_references":5,"next":{"headline":"crypto: akcipher - default implementation for setting a private key","id":"CVE-2022-50731"},"packages":[],"prev":{"headline":"ksmbd: Fix resource leak in ksmbd_session_rpc_open()","id":"CVE-2022-50729"},"products":["Linux"],"published":"2025-12-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A race condition in the Linux kernel ext4 filesystem triggers a kernel warning during inode eviction, potentially causing a denial of service.","url":"https://insights.sbomify.com/CVE-2022-50730/"}