CVE-2026-31751
Description
In the Linux kernel, the following vulnerability has been resolved: comedi: dt2815: add hardware detection to prevent crash The dt2815 driver crashes when attached to I/O ports without actual hardware present. This occurs because syzkaller or users can attach the driver to arbitrary I/O addresses via COMEDI_DEVCONFIG ioctl. When no hardware exists at the specified port, inb() operations return 0xff (floating bus), but outb() operations can trigger page faults due to undefined behavior, especially under race conditions: BUG: unable to handle page fault for address: 000000007fffff90 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page RIP: 0010:dt2815_attach+0x6e0/0x1110 Add hardware detection by reading the status register before attempting any write operations. If the read returns 0xff, assume no hardware is present and fail the attach with -ENODEV. This prevents crashes from outb() operations on non-existent hardware.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| sles | affected | | |
| debian | bookworm | fixed | 6.1.170-1 |
| debian | forky | fixed | 6.19.12-1 |
| debian | sid | fixed | 6.19.12-1 |
| debian | trixie | fixed | 6.12.85-1 |
| debian | bullseye | fixed | 6.1.170-1~deb11u1 |
| linux-kernel | affected | 5.10.253 | |
| linux-kernel | 7.0 | affected | |
References
- https://git.kernel.org/stable/c/0dcf33994b8dcf3db36530fb7e2cf9f89e5cbac3
- https://git.kernel.org/stable/c/34b13250c618d7441508c6ef369144aa8a9b9bfa
- https://git.kernel.org/stable/c/34c8b3a91bdfbe4573650b4cd750ef639101fdc5
- https://git.kernel.org/stable/c/65c528fbeddd88478c210052f6c7b21be4973156
- https://git.kernel.org/stable/c/8d63161837f1bf8810dbcd2a583c2bbf5ca6d733
- https://git.kernel.org/stable/c/93853512f565e625df2397f0d8050d6aafd7c3ad
- https://git.kernel.org/stable/c/d2a786efdb9971f2a647724625da5bbecc994dc9
- https://git.kernel.org/stable/c/d5d9df8b08d68d083ac57abc2c887dfb1f31af63
- https://www.suse.com/security/cve/CVE-2026-31751.html
- https://security-tracker.debian.org/tracker/CVE-2026-31751
CWEs
CWE-362
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.