{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89449 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89449 is a memory corruption vulnerability in Linux, published on 11 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-89449 and fix it if it is affected.\n\nWhat it is: CVE-2026-89449 is a memory corruption vulnerability in Linux, published on 11 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-89449 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-89449/ (Markdown: https://insights.sbomify.com/CVE-2026-89449/index.md)","id":"CVE-2026-89449","markdown":"https://insights.sbomify.com/CVE-2026-89449/index.md","name":"CVE-2026-89449","record":{"aliases":["BELL-CVE-2026-89449","DEBIAN-CVE-2026-89449","GHSA-3365-g9v5-8jg9","UBUNTU-CVE-2026-89449"],"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 memory leak in the Linux kernel IOMMU subsystem allows local attackers to exhaust system memory via ioctl calls, leading to denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\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.","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":"iommu: Fix dev_iommu memory leak when device_add fails in iommu_mock_device_add","id":"CVE-2026-89449","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"iommu/tegra241-cmdqv: Reject a vSID wider than the SID_MATCH field","id":"CVE-2026-89450"},"packages":[],"prev":{"headline":"iommu/vt-d: Force requesting ACS when tboot is enabled","id":"CVE-2026-89448"},"products":["Linux"],"published":"2026-09-11","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-19","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel IOMMU subsystem allows local attackers to exhaust system memory via ioctl calls, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-89449/"}