{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92503 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-92503 is a vulnerability in Linux, published on 17 Sep 2026. 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-2026-92503 and fix it if it is affected.\n\nWhat it is: CVE-2026-92503 is a vulnerability in Linux, published on 17 Sep 2026. 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-2026-92503 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-2026-92503/ (Markdown: https://insights.sbomify.com/CVE-2026-92503/index.md)","id":"CVE-2026-92503","markdown":"https://insights.sbomify.com/CVE-2026-92503/index.md","name":"CVE-2026-92503","record":{"aliases":["AZL-102104","BELL-CVE-2026-92503","DEBIAN-CVE-2026-92503","GHSA-4ppx-vw73-jjc6","UBUNTU-CVE-2026-92503"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel ext4","requires_auth":"none","summary":"A race condition in the Linux kernel ext4 filesystem causes an ABBA deadlock during concurrent extended attribute operations, leading to system 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: fix ABBA deadlock in ext4_xattr_inode_cache_find()\n\nSyzbot/stress-ng reported an ABBA deadlock in ext4 when exercising\nconcurrent xattr workloads (using the ea_inode mount/format option).\n\nThe deadlock occurs between the running transaction and the eviction\nthread:\n- Task 1 (stress-ng): Holds a reference to a shared mbcache_entry (ce)\n  and calls ext4_xattr_inode_cache_find() -\u003e ext4_iget() to retrieve\n  the corresponding EA inode. Since the EA inode is currently being\n  evicted, ext4_iget() blocks in __wait_on_freeing_inode() waiting for\n  eviction to complete.\n- Task 2 (eviction thread): Currently evicting the same EA inode in\n  ext4_evict_ea_inode(). It calls mb_cache_entry_wait_unused(oe) which\n  blocks waiting for Task 1 to release the reference to the mbcache_entry.\n\nTo break this deadlock, implement a new ext4_iget() configuration flag\nnamed EXT4_IGET_NOWAIT. When set, perform a non-blocking lookup of the\ninode via VFS's find_inode_nowait() API.\n\nIf the inode is currently being evicted (marked with I_FREEING or\nI_WILL_FREE) or created (I_CREATING), or if it is not present in the VFS\ninode cache (cache miss), simply skip it (returning -ENOENT) rather than\nwaiting for eviction/creation to complete, breaking the ABBA cycle.\n\nSince we return -ENOENT immediately on a cache miss, we never attempt to\nallocate a new inode or call iget_locked(), completely eliminating any\nTOCTOU race window.\n\nIf the returned inode is I_NEW, wait for its initialization to clear via\nwait_on_new_inode(). If initialization fails and the inode is unhashed\nduring wait_on_new_inode() waking up (e.g., due to an I/O read error in\nanother thread), safely drop the reference and return -ENOENT. This\nunhashed check is executed unconditionally on all cache-hit pathways to\nproperly handle concurrent initialization failures.\n\nFinally, standard validation checks (including is_bad_inode,\nEXT4_EA_INODE_FL, file_acl, and xattr flags) are executed as normal inside\ncheck_igot_inode() to fully guarantee VFS-layer safety.\n\nIn ext4_xattr_inode_cache_find(), invoke ext4_iget() with the new\nEXT4_IGET_NOWAIT flag to perform the non-blocking cache search.","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 ABBA deadlock in ext4_xattr_inode_cache_find()","id":"CVE-2026-92503","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"thermal: intel: int3400: clean up ODVP on probe failures","id":"CVE-2026-92504"},"packages":[],"prev":{"headline":"ext4: clear stale xarray tags on folios skipped during writeback","id":"CVE-2026-92502"},"products":["Linux"],"published":"2026-09-17","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-10-21","vendors":["Linux"]},"summary":"A race condition in the Linux kernel ext4 filesystem causes an ABBA deadlock during concurrent extended attribute operations, leading to system denial of service.","url":"https://insights.sbomify.com/CVE-2026-92503/"}