{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2023-53795", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2025-12-08T23:58:35.274Z", "datePublished": "2025-12-09T00:00:51.992Z", "dateUpdated": "2025-12-09T00:00:51.992Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2025-12-09T00:00:51.992Z"}, "descriptions": [{"lang": "en", "value": "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->ictx, cmd->id, 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->ictx, 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 <0f> 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 <TASK>\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."}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["drivers/iommu/iommufd/device.c", "drivers/iommu/iommufd/iommufd_private.h", "drivers/iommu/iommufd/main.c"], "versions": [{"version": "2ff4bed7fee72ba1abfcff5f11ae8f8e570353f2", "lessThan": "495b327435b0298e9b3b434f5834d459a93673ce", "status": "affected", "versionType": "git"}, {"version": "2ff4bed7fee72ba1abfcff5f11ae8f8e570353f2", "lessThan": "99f98a7c0d6985d5507c8130a981972e4b7b3bdc", "status": "affected", "versionType": "git"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["drivers/iommu/iommufd/device.c", "drivers/iommu/iommufd/iommufd_private.h", "drivers/iommu/iommufd/main.c"], "versions": [{"version": "6.2", "status": "affected"}, {"version": "0", "lessThan": "6.2", "status": "unaffected", "versionType": "semver"}, {"version": "6.4.8", "lessThanOrEqual": "6.4.*", "status": "unaffected", "versionType": "semver"}, {"version": "6.5", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "cpeApplicability": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.2", "versionEndExcluding": "6.4.8"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.2", "versionEndExcluding": "6.5"}]}]}], "references": [{"url": "https://git.kernel.org/stable/c/495b327435b0298e9b3b434f5834d459a93673ce"}, {"url": "https://git.kernel.org/stable/c/99f98a7c0d6985d5507c8130a981972e4b7b3bdc"}], "title": "iommufd: IOMMUFD_DESTROY should not increase the refcount", "x_generator": {"engine": "bippy-1.2.0"}}}}

{}

{"cveTags": [], "descriptions": [{"lang": "en", "value": "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->ictx, cmd->id, 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->ictx, 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 <0f> 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 <TASK>\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."}], "id": "CVE-2023-53795", "lastModified": "2025-12-09T18:37:13.640", "metrics": {}, "published": "2025-12-09T01:16:51.080", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/495b327435b0298e9b3b434f5834d459a93673ce"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/99f98a7c0d6985d5507c8130a981972e4b7b3bdc"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Awaiting Analysis"}

{"bugzilla": {"description": "kernel: iommufd: IOMMUFD_DESTROY should not increase the refcount", "id": "2420238", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2420238"}, "csaw": false, "cvss3": {"cvss3_base_score": "7.0", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H", "status": "draft"}, "details": ["In the Linux kernel, the following vulnerability has been resolved:\niommufd: IOMMUFD_DESTROY should not increase the refcount\nsyzkaller found a race where IOMMUFD_DESTROY increments the refcount:\nobj = iommufd_get_object(ucmd->ictx, cmd->id, IOMMUFD_OBJ_ANY);\nif (IS_ERR(obj))\nreturn PTR_ERR(obj);\niommufd_ref_to_users(obj);\n/* See iommufd_ref_to_users() */\nif (!iommufd_object_destroy_user(ucmd->ictx, obj))\nAs part of the sequence to join the two existing primitives together.\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:\nWARNING: CPU: 0 PID: 3076 at drivers/iommu/iommufd/device.c:477 iommufd_access_destroy+0x18/0x20 drivers/iommu/iommufd/device.c:478\nModules linked in:\nCPU: 0 PID: 3076 Comm: syz-executor.0 Not tainted 6.3.0-rc1-syzkaller #0\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023\nRIP: 0010:iommufd_access_destroy+0x18/0x20 drivers/iommu/iommufd/device.c:477\nCode: 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 <0f> 0b c3 0f 1f 44 00 00 41 57 41 56 41 55 4c 8d ae d0 00 00 00 41\nRSP: 0018:ffffc90003067e08 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffff888109ea0300 RCX: 0000000000000000\nRDX: 0000000000000001 RSI: 0000000000000000 RDI: 00000000ffffffff\nRBP: 0000000000000004 R08: 0000000000000000 R09: ffff88810bbb3500\nR10: ffff88810bbb3e48 R11: 0000000000000000 R12: ffffc90003067e88\nR13: ffffc90003067ea8 R14: ffff888101249800 R15: 00000000fffffffe\nFS: 00007ff7254fe6c0(0000) GS:ffff888237c00000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000555557262da8 CR3: 000000010a6fd000 CR4: 0000000000350ef0\nCall Trace:\n<TASK>\niommufd_test_create_access drivers/iommu/iommufd/selftest.c:596 [inline]\niommufd_test+0x71c/0xcf0 drivers/iommu/iommufd/selftest.c:813\niommufd_fops_ioctl+0x10f/0x1b0 drivers/iommu/iommufd/main.c:337\nvfs_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\ndo_syscall_x64 arch/x86/entry/common.c:50 [inline]\ndo_syscall_64+0x38/0x80 arch/x86/entry/common.c:80\nentry_SYSCALL_64_after_hwframe+0x63/0xcd\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.\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."], "name": "CVE-2023-53795", "package_state": [{"cpe": "cpe:/o:redhat:enterprise_linux:10", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 10"}, {"cpe": "cpe:/o:redhat:enterprise_linux:6", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 6"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 9"}], "public_date": "2025-12-09T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2023-53795\nhttps://nvd.nist.gov/vuln/detail/CVE-2023-53795\nhttps://lore.kernel.org/linux-cve-announce/2025120941-CVE-2023-53795-f912@gregkh/T"], "threat_severity": "Moderate"}