{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89515 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89515 is a 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-89515 and fix it if it is affected.\n\nWhat it is: CVE-2026-89515 is a 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-89515 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-89515/ (Markdown: https://insights.sbomify.com/CVE-2026-89515/index.md)","id":"CVE-2026-89515","markdown":"https://insights.sbomify.com/CVE-2026-89515/index.md","name":"CVE-2026-89515","record":{"aliases":["AZL-100319","BELL-CVE-2026-89515","DEBIAN-CVE-2026-89515","GHSA-c4r4-q33m-rp34","UBUNTU-CVE-2026-89515"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can read uninitialized kernel memory via SCSI ioctl calls, potentially exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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\nscsi: core: Fill in DMA padding bytes in scsi_alloc_sgtables()\n\nDuring fuzz testing, the following issue was discovered:\n\nBUG: KMSAN: uninit-value in __dma_map_sg_attrs+0x217/0x310\n __dma_map_sg_attrs+0x217/0x310\n dma_map_sg_attrs+0x4a/0x70\n ata_qc_issue+0x9f8/0x1420\n __ata_scsi_queuecmd+0x1657/0x1740\n ata_scsi_queuecmd+0x79a/0x920\n scsi_queue_rq+0x4472/0x4f40\n blk_mq_dispatch_rq_list+0x1cca/0x3ee0\n __blk_mq_sched_dispatch_requests+0x458/0x630\n blk_mq_sched_dispatch_requests+0x15b/0x340\n __blk_mq_run_hw_queue+0xe5/0x250\n __blk_mq_delay_run_hw_queue+0x138/0x780\n blk_mq_run_hw_queue+0x4bb/0x7e0\n blk_mq_sched_insert_request+0x2a7/0x4c0\n blk_execute_rq+0x497/0x8a0\n sg_io+0xbe0/0xe20\n scsi_ioctl+0x2b36/0x3c60\n sr_block_ioctl+0x319/0x440\n blkdev_ioctl+0x80f/0xd70\n __se_sys_ioctl+0x219/0x420\n __x64_sys_ioctl+0x93/0xe0\n x64_sys_call+0x1d6c/0x3ad0\n do_syscall_64+0x4c/0xa0\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8\n\nUninit was created at:\n __alloc_pages+0x5c0/0xc80\n alloc_pages+0xe0e/0x1050\n blk_rq_map_user_iov+0x2b77/0x6100\n blk_rq_map_user_io+0x2fa/0x4d0\n sg_io+0xad6/0xe20\n scsi_ioctl+0x2b36/0x3c60\n sr_block_ioctl+0x319/0x440\n blkdev_ioctl+0x80f/0xd70\n __se_sys_ioctl+0x219/0x420\n __x64_sys_ioctl+0x93/0xe0\n x64_sys_call+0x1d6c/0x3ad0\n do_syscall_64+0x4c/0xa0\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8\n\nBytes 14-15 of 16 are uninitialized\nMemory access of size 16 starts at ffff88800cbdb000\n\nWhen processing the last unaligned element of the scatterlist, it is\nsupplemented with missing bytes in the amount of pad_len.  These bytes\nremain uninitialized, which leads to a problem.\n\nExtend last_sg-\u003elength by pad_len first, then use sg_zero_buffer() to\nzero those pad_len bytes.  sg_zero_buffer() uses sg_miter internally,\nwhich correctly handles sg entries spanning multiple pages and padding\nthat crosses a page boundary.\n\nFound by Linux Verification Center (linuxtesting.org) with Syzkaller.","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":"scsi: core: Fill in DMA padding bytes in scsi_alloc_sgtables()","id":"CVE-2026-89515","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"sched_ext: Don't BUG_ON a destroyed DSQ in process_deferred_reenq_users","id":"CVE-2026-89516"},"packages":[],"prev":{"headline":"scsi: fnic: Use GFP_ATOMIC for VLAN alloc under spinlock","id":"CVE-2026-89514"},"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 local attacker can read uninitialized kernel memory via SCSI ioctl calls, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-89515/"}