CVE-2026-89515: scsi: core: Fill in DMA padding bytes in scsi_alloc_sgtables()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 1aa6df61cef1f47f503c3ccf60d08c4dd931fdc1, 28ed5343666ff424ce5e248fa1c5a402303b4aff, 626147717bea776b61ed3631d2c26283760c4cc4.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1aa6df61cef1f47f503c3ccf60d08c4dd931fdc1, 28ed5343666ff424ce5e248fa1c5a402303b4aff, 626147717bea776b61ed3631d2c26283760c4cc4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: scsi: core: Fill in DMA padding bytes in scsi_alloc_sgtables() During fuzz testing, the following issue was discovered: BUG: KMSAN: uninit-value in __dma_map_sg_attrs+0x217/0x310 __dma_map_sg_attrs+0x217/0x310 dma_map_sg_attrs+0x4a/0x70 ata_qc_issue+0x9f8/0x1420 __ata_scsi_queuecmd+0x1657/0x1740 ata_scsi_queuecmd+0x79a/0x920 scsi_queue_rq+0x4472/0x4f40 blk_mq_dispatch_rq_list+0x1cca/0x3ee0 __blk_mq_sched_dispatch_requests+0x458/0x630 blk_mq_sched_dispatch_requests+0x15b/0x340 __blk_mq_run_hw_queue+0xe5/0x250 __blk_mq_delay_run_hw_queue+0x138/0x780 blk_mq_run_hw_queue+0x4bb/0x7e0 blk_mq_sched_insert_request+0x2a7/0x4c0 blk_execute_rq+0x497/0x8a0 sg_io+0xbe0/0xe20 scsi_ioctl+0x2b36/0x3c60 sr_block_ioctl+0x319/0x440 blkdev_ioctl+0x80f/0xd70 __se_sys_ioctl+0x219/0x420 __x64_sys_ioctl+0x93/0xe0 x64_sys_call+0x1d6c/0x3ad0 do_syscall_64+0x4c/0xa0 entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Uninit was created at: __alloc_pages+0x5c0/0xc80 alloc_pages+0xe0e/0x1050 blk_rq_map_user_iov+0x2b77/0x6100 blk_rq_map_user_io+0x2fa/0x4d0 sg_io+0xad6/0xe20 scsi_ioctl+0x2b36/0x3c60 sr_block_ioctl+0x319/0x440 blkdev_ioctl+0x80f/0xd70 __se_sys_ioctl+0x219/0x420 __x64_sys_ioctl+0x93/0xe0 x64_sys_call+0x1d6c/0x3ad0 do_syscall_64+0x4c/0xa0 entry_SYSCALL_64_after_hwframe+0x6e/0xd8 Bytes 14-15 of 16 are uninitialized Memory access of size 16 starts at ffff88800cbdb000 When processing the last unaligned element of the scatterlist, it is supplemented with missing bytes in the amount of pad_len. These bytes remain uninitialized, which leads to a problem. Extend last_sg->length by pad_len first, then use sg_zero_buffer() to zero those pad_len bytes. sg_zero_buffer() uses sg_miter internally, which correctly handles sg entries spanning multiple pages and padding that crosses a page boundary. Found by Linux Verification Center (linuxtesting.org) with Syzkaller.
- Published
- Sep 11, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.25affected
- 40b01b9bbdf51ae543a04744283bf2d56c4a6afa and later · before 1aa6df61cef1f47f503c3ccf60d08c4dd931fdc1affected · git
- 40b01b9bbdf51ae543a04744283bf2d56c4a6afa and later · before 6da140ebdfdd6aa3773945f2c0ebba01d2ef33d8affected · git
- 40b01b9bbdf51ae543a04744283bf2d56c4a6afa and later · before fd2cbe08c6ccba7fc1ddb830653a93bb7e2d833caffected · git
- 40b01b9bbdf51ae543a04744283bf2d56c4a6afa and later · before 28ed5343666ff424ce5e248fa1c5a402303b4affaffected · git
- 40b01b9bbdf51ae543a04744283bf2d56c4a6afa and later · before a4353ec7742bdf87dcdde5875270feb3a1982a51affected · git
- 40b01b9bbdf51ae543a04744283bf2d56c4a6afa and later · before e7143c3f4e5c0a7986733c6f27009274bf6c4264affected · git
- 40b01b9bbdf51ae543a04744283bf2d56c4a6afa and later · before 6fd1cce5018fdcc8d928e00a6a1dd2997d5b9409affected · git
- 40b01b9bbdf51ae543a04744283bf2d56c4a6afa and later · before 626147717bea776b61ed3631d2c26283760c4cc4affected · git
- before 2.6.25not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-89513Sep 11, 2026 · RISC-V: KVM: Fix PMU event info array size overflow35Monitor
- ← EarlierCVE-2026-89514Sep 11, 2026 · scsi: fnic: Use GFP_ATOMIC for VLAN alloc under spinlock0Monitor
- Later →CVE-2026-89516Sep 11, 2026 · sched_ext: Don't BUG_ON a destroyed DSQ in process_deferred_reenq_users0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1aa6df61cef1f47f503c3ccf60d08c4dd931fdc1 | Vendor (CNA) |
| Linux Linux | 28ed5343666ff424ce5e248fa1c5a402303b4aff | Vendor (CNA) |
| Linux Linux | 626147717bea776b61ed3631d2c26283760c4cc4 | Vendor (CNA) |
| Linux Linux | 6da140ebdfdd6aa3773945f2c0ebba01d2ef33d8 | Vendor (CNA) |
| Linux Linux | 6fd1cce5018fdcc8d928e00a6a1dd2997d5b9409 | Vendor (CNA) |
| Linux Linux | a4353ec7742bdf87dcdde5875270feb3a1982a51 | Vendor (CNA) |
| Linux Linux | e7143c3f4e5c0a7986733c6f27009274bf6c4264 | Vendor (CNA) |
| Linux Linux | fd2cbe08c6ccba7fc1ddb830653a93bb7e2d833c | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/28ed5343666ff424ce5e248fa1c5a402303b4aff
- git.kernel.org/stable/c/626147717bea776b61ed3631d2c26283760c4cc4
- git.kernel.org/stable/c/6da140ebdfdd6aa3773945f2c0ebba01d2ef33d8
- git.kernel.org/stable/c/6fd1cce5018fdcc8d928e00a6a1dd2997d5b9409
- git.kernel.org/stable/c/a4353ec7742bdf87dcdde5875270feb3a1982a51
- git.kernel.org/stable/c/e7143c3f4e5c0a7986733c6f27009274bf6c4264
- git.kernel.org/stable/c/fd2cbe08c6ccba7fc1ddb830653a93bb7e2d833c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.