{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90387 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90387 is a high-severity 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-90387 and fix it if it is affected.\n\nWhat it is: CVE-2026-90387 is a high-severity 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-90387 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-90387/ (Markdown: https://insights.sbomify.com/CVE-2026-90387/index.md)","id":"CVE-2026-90387","markdown":"https://insights.sbomify.com/CVE-2026-90387/index.md","name":"CVE-2026-90387","record":{"aliases":["AZL-102470","BELL-CVE-2026-90387","DEBIAN-CVE-2026-90387","GHSA-rw87-3jgx-gg57","UBUNTU-CVE-2026-90387"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"Incorrect virtual address handling in Linux kernel swiotlb dynamic pools can cause memory free failures, potentially leading to system crashes.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\nswiotlb: Preserve allocation virtual address for dynamic pools\n\nswiotlb_alloc_tlb() can allocate from the DMA atomic pool when a decrypted\npool is needed from atomic context. With CONFIG_DMA_DIRECT_REMAP, the\natomic pool is backed by remapped virtual addresses, which are not the same\nas the direct-map addresses returned by phys_to_virt().\n\nswiotlb_init_io_tlb_pool() currently reconstructs the pool virtual address\nfrom the physical start address. For atomic-pool backed allocations this\nstores the wrong address in pool-\u003evaddr. Later, swiotlb_free_tlb() passes\nthat address to dma_free_from_pool(), which will fail to recognize the\nchunk\n\nPass the virtual address returned by the allocation path into\nswiotlb_init_io_tlb_pool(), and store that address in pool-\u003evaddr. This\nkeeps the pool free path using the same virtual address as the allocator.","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":"swiotlb: Preserve allocation virtual address for dynamic pools","id":"CVE-2026-90387","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"iommu/dma: Check atomic pool allocation result directly","id":"CVE-2026-90388"},"packages":[],"prev":{"headline":"i3c: dw: avoid shift-out-of-bounds when DAA assigns no devices","id":"CVE-2026-90386"},"products":["Linux"],"published":"2026-09-17","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-10-19","vendors":["Linux"]},"summary":"Incorrect virtual address handling in Linux kernel swiotlb dynamic pools can cause memory free failures, potentially leading to system crashes.","url":"https://insights.sbomify.com/CVE-2026-90387/"}