GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

FKIE_CVE-2026-89449

Vulnerability from fkie_nvd - Published: 2026-09-11 20:19 - Updated: 2026-09-11 20:19
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved: iommu: Fix dev_iommu memory leak when device_add fails in iommu_mock_device_add iommu_mock_device_add() first calls iommu_fwspec_init(), which on success allocates both dev->iommu (via dev_iommu_get()) and dev->iommu->fwspec. If the subsequent device_add(dev) call fails, the error path only calls iommu_fwspec_free(dev), which frees fwspec but leaves dev->iommu still allocated. This triggers the following kmemleak report when fuzzing with Syzkaller: BUG: memory leak unreferenced object 0xffff888011e0a200 (size 192): comm "syz.1.1695", pid 24885, jiffies 4295222527 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 ad 4e ad de .............N.. ff ff ff ff 00 00 00 00 ff ff ff ff ff ff ff ff ................ backtrace (crc 25df5bb3): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4575 [inline] slab_alloc_node mm/slub.c:4899 [inline] __kmalloc_cache_noprof+0x47a/0x710 mm/slub.c:5415 kmalloc_noprof include/linux/slab.h:950 [inline] kzalloc_noprof include/linux/slab.h:1188 [inline] dev_iommu_get+0x10c/0x1a0 drivers/iommu/iommu.c:408 iommu_fwspec_init+0x288/0x4d0 drivers/iommu/iommu.c:3087 iommu_mock_device_add+0x46/0xb0 drivers/iommu/iommu.c:385 mock_dev_create drivers/iommu/iommufd/selftest.c:1025 [inline] iommufd_test_mock_domain drivers/iommu/iommufd/selftest.c:1066 [inline] iommufd_test+0x2f8a/0x6190 drivers/iommu/iommufd/selftest.c:2072 iommufd_fops_ioctl+0x367/0x540 drivers/iommu/iommufd/main.c:533 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x116/0x800 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Fix this by calling dev_iommu_free(dev) instead of iommu_fwspec_free(dev) in the device_add() failure path. dev_iommu_free() frees both fwspec and the outer dev_iommu struct and clears dev->iommu.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/b7b0b3851474883d4aba6ed72da87141204b23e5
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/eaf44262af24810d16800b988c92dfce90f73370
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/f80f3acb69164800051ecdee871b6b006cbc2e66
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/iommu/iommu.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "f80f3acb69164800051ecdee871b6b006cbc2e66",
              "status": "affected",
              "version": "2a918911ed3d0841923525ed0fe707762ee78844",
              "versionType": "git"
            },
            {
              "lessThan": "eaf44262af24810d16800b988c92dfce90f73370",
              "status": "affected",
              "version": "2a918911ed3d0841923525ed0fe707762ee78844",
              "versionType": "git"
            },
            {
              "lessThan": "b7b0b3851474883d4aba6ed72da87141204b23e5",
              "status": "affected",
              "version": "2a918911ed3d0841923525ed0fe707762ee78844",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "1daf67217b0d0bf88ef7208d7fbeefe2378c6590",
              "versionType": "git"
            },
            {
              "lessThan": "6.18",
              "status": "affected",
              "version": "6.17.3",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/iommu/iommu.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.18"
            },
            {
              "lessThan": "6.18",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.50",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.2.*",
              "status": "unaffected",
              "version": "7.2.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.3-rc1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\niommu: Fix dev_iommu memory leak when device_add fails in iommu_mock_device_add\n\niommu_mock_device_add() first calls iommu_fwspec_init(), which on\nsuccess allocates both dev-\u003eiommu (via dev_iommu_get()) and\ndev-\u003eiommu-\u003efwspec. If the subsequent device_add(dev) call fails,\nthe error path only calls iommu_fwspec_free(dev), which frees\nfwspec but leaves dev-\u003eiommu still allocated.\n\nThis triggers the following kmemleak report when fuzzing with Syzkaller:\n\nBUG: memory leak\nunreferenced object 0xffff888011e0a200 (size 192):\n  comm \"syz.1.1695\", pid 24885, jiffies 4295222527\n  hex dump (first 32 bytes):\n    00 00 00 00 00 00 00 00 00 00 00 00 ad 4e ad de  .............N..\n    ff ff ff ff 00 00 00 00 ff ff ff ff ff ff ff ff  ................\n  backtrace (crc 25df5bb3):\n    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]\n    slab_post_alloc_hook mm/slub.c:4575 [inline]\n    slab_alloc_node mm/slub.c:4899 [inline]\n    __kmalloc_cache_noprof+0x47a/0x710 mm/slub.c:5415\n    kmalloc_noprof include/linux/slab.h:950 [inline]\n    kzalloc_noprof include/linux/slab.h:1188 [inline]\n    dev_iommu_get+0x10c/0x1a0 drivers/iommu/iommu.c:408\n    iommu_fwspec_init+0x288/0x4d0 drivers/iommu/iommu.c:3087\n    iommu_mock_device_add+0x46/0xb0 drivers/iommu/iommu.c:385\n    mock_dev_create drivers/iommu/iommufd/selftest.c:1025 [inline]\n    iommufd_test_mock_domain drivers/iommu/iommufd/selftest.c:1066 [inline]\n    iommufd_test+0x2f8a/0x6190 drivers/iommu/iommufd/selftest.c:2072\n    iommufd_fops_ioctl+0x367/0x540 drivers/iommu/iommufd/main.c:533\n    vfs_ioctl fs/ioctl.c:51 [inline]\n    __do_sys_ioctl fs/ioctl.c:597 [inline]\n    __se_sys_ioctl fs/ioctl.c:583 [inline]\n    __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n    do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n    do_syscall_64+0x116/0x800 arch/x86/entry/syscall_64.c:94\n    entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFix this by calling dev_iommu_free(dev) instead of iommu_fwspec_free(dev)\nin the device_add() failure path. dev_iommu_free() frees both fwspec\nand the outer dev_iommu struct and clears dev-\u003eiommu."
    }
  ],
  "id": "CVE-2026-89449",
  "lastModified": "2026-09-11T20:19:25.473",
  "metrics": {},
  "published": "2026-09-11T20:19:25.473",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/b7b0b3851474883d4aba6ed72da87141204b23e5"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/eaf44262af24810d16800b988c92dfce90f73370"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/f80f3acb69164800051ecdee871b6b006cbc2e66"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.