{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50845 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50845 is a denial of service vulnerability in Linux, published on 30 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-50845 and fix it if it is affected.\n\nWhat it is: CVE-2022-50845 is a denial of service vulnerability in Linux, published on 30 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-50845 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-50845/ (Markdown: https://insights.sbomify.com/CVE-2022-50845/index.md)","id":"CVE-2022-50845","markdown":"https://insights.sbomify.com/CVE-2022-50845/index.md","name":"CVE-2022-50845","record":{"aliases":["DEBIAN-CVE-2022-50845","GHSA-cmjr-fqjm-v74q","UBUNTU-CVE-2022-50845"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel ext4","requires_auth":"low_privilege","summary":"A local attacker can cause an inode leak in the ext4 filesystem by triggering an error path during extended attribute creation, leading to resource exhaustion.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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: fix inode leak in ext4_xattr_inode_create() on an error path\n\nThere is issue as follows when do setxattr with inject fault:\n\n[localhost]# fsck.ext4  -fn  /dev/sda\ne2fsck 1.46.6-rc1 (12-Sep-2022)\nPass 1: Checking inodes, blocks, and sizes\nPass 2: Checking directory structure\nPass 3: Checking directory connectivity\nPass 4: Checking reference counts\nUnattached zero-length inode 15.  Clear? no\n\nUnattached inode 15\nConnect to /lost+found? no\n\nPass 5: Checking group summary information\n\n/dev/sda: ********** WARNING: Filesystem still has errors **********\n\n/dev/sda: 15/655360 files (0.0% non-contiguous), 66755/2621440 blocks\n\nThis occurs in 'ext4_xattr_inode_create()'. If 'ext4_mark_inode_dirty()'\nfails, dropping i_nlink of the inode is needed. Or will lead to inode leak.","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: fix inode leak in ext4_xattr_inode_create() on an error path","id":"CVE-2022-50845","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":0,"n_references":8,"next":{"headline":"mmc: via-sdmmc: fix return value check of mmc_add_host()","id":"CVE-2022-50846"},"packages":[],"prev":{"headline":"drm/amdgpu: Fix type of second parameter in odn_edit_dpm_table() callback","id":"CVE-2022-50844"},"products":["Linux"],"published":"2025-12-30","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 local attacker can cause an inode leak in the ext4 filesystem by triggering an error path during extended attribute creation, leading to resource exhaustion.","url":"https://insights.sbomify.com/CVE-2022-50845/"}