{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2023-53795 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-53795 is a high-severity vulnerability in Linux, published on 9 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-2023-53795 and fix it if it is affected.\n\nWhat it is: CVE-2023-53795 is a high-severity vulnerability in Linux, published on 9 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-2023-53795 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-2023-53795/ (Markdown: https://insights.sbomify.com/CVE-2023-53795/index.md)","id":"CVE-2023-53795","markdown":"https://insights.sbomify.com/CVE-2023-53795/index.md","name":"CVE-2023-53795","record":{"aliases":["BELL-CVE-2023-53795","DEBIAN-CVE-2023-53795","GHSA-54v3-2q3m-7783","UBUNTU-CVE-2023-53795"],"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's iommufd subsystem allows local attackers to trigger spurious failures and potential denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\niommufd: IOMMUFD_DESTROY should not increase the refcount\n\nsyzkaller found a race where IOMMUFD_DESTROY increments the refcount:\n\n       obj = iommufd_get_object(ucmd-\u003eictx, cmd-\u003eid, IOMMUFD_OBJ_ANY);\n       if (IS_ERR(obj))\n               return PTR_ERR(obj);\n       iommufd_ref_to_users(obj);\n       /* See iommufd_ref_to_users() */\n       if (!iommufd_object_destroy_user(ucmd-\u003eictx, obj))\n\nAs part of the sequence to join the two existing primitives together.\n\nAllowing the refcount the be elevated without holding the destroy_rwsem\nviolates the assumption that all temporary refcount elevations are\nprotected by destroy_rwsem. Racing IOMMUFD_DESTROY with\niommufd_object_destroy_user() will cause spurious failures:\n\n  WARNING: CPU: 0 PID: 3076 at drivers/iommu/iommufd/device.c:477 iommufd_access_destroy+0x18/0x20 drivers/iommu/iommufd/device.c:478\n  Modules linked in:\n  CPU: 0 PID: 3076 Comm: syz-executor.0 Not tainted 6.3.0-rc1-syzkaller #0\n  Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023\n  RIP: 0010:iommufd_access_destroy+0x18/0x20 drivers/iommu/iommufd/device.c:477\n  Code: e8 3d 4e 00 00 84 c0 74 01 c3 0f 0b c3 0f 1f 44 00 00 f3 0f 1e fa 48 89 fe 48 8b bf a8 00 00 00 e8 1d 4e 00 00 84 c0 74 01 c3 \u003c0f\u003e 0b c3 0f 1f 44 00 00 41 57 41 56 41 55 4c 8d ae d0 00 00 00 41\n  RSP: 0018:ffffc90003067e08 EFLAGS: 00010246\n  RAX: 0000000000000000 RBX: ffff888109ea0300 RCX: 0000000000000000\n  RDX: 0000000000000001 RSI: 0000000000000000 RDI: 00000000ffffffff\n  RBP: 0000000000000004 R08: 0000000000000000 R09: ffff88810bbb3500\n  R10: ffff88810bbb3e48 R11: 0000000000000000 R12: ffffc90003067e88\n  R13: ffffc90003067ea8 R14: ffff888101249800 R15: 00000000fffffffe\n  FS:  00007ff7254fe6c0(0000) GS:ffff888237c00000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 0000555557262da8 CR3: 000000010a6fd000 CR4: 0000000000350ef0\n  Call Trace:\n   \u003cTASK\u003e\n   iommufd_test_create_access drivers/iommu/iommufd/selftest.c:596 [inline]\n   iommufd_test+0x71c/0xcf0 drivers/iommu/iommufd/selftest.c:813\n   iommufd_fops_ioctl+0x10f/0x1b0 drivers/iommu/iommufd/main.c:337\n   vfs_ioctl fs/ioctl.c:51 [inline]\n   __do_sys_ioctl fs/ioctl.c:870 [inline]\n   __se_sys_ioctl fs/ioctl.c:856 [inline]\n   __x64_sys_ioctl+0x84/0xc0 fs/ioctl.c:856\n   do_syscall_x64 arch/x86/entry/common.c:50 [inline]\n   do_syscall_64+0x38/0x80 arch/x86/entry/common.c:80\n   entry_SYSCALL_64_after_hwframe+0x63/0xcd\n\nThe solution is to not increment the refcount on the IOMMUFD_DESTROY path\nat all. Instead use the xa_lock to serialize everything. The refcount\ncheck == 1 and xa_erase can be done under a single critical region. This\navoids the need for any refcount incrementing.\n\nIt has the downside that if userspace races destroy with other operations\nit will get an EBUSY instead of waiting, but this is kind of racing is\nalready dangerous.","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":"iommufd: IOMMUFD_DESTROY should not increase the refcount","id":"CVE-2023-53795","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"f2fs: fix information leak in f2fs_move_inline_dirents()","id":"CVE-2023-53796"},"packages":[],"prev":{"headline":"cifs: fix session state check in reconnect to avoid use-after-free issue","id":"CVE-2023-53794"},"products":["Linux"],"published":"2025-12-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-05","vendors":["Linux"]},"summary":"A race condition in the Linux kernel's iommufd subsystem allows local attackers to trigger spurious failures and potential denial of service.","url":"https://insights.sbomify.com/CVE-2023-53795/"}