Quick answers
- Is CVE-2026-98296 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-98296 being exploited in the wild.
- How severe is CVE-2026-98296?
- Informational severity, published 6 October 2026.
- Which products and versions are affected?
- Linux Kernels with btintel_pcie driver prior to commit 4b837ebd0ea21ae5cc26f02dc042edc6fe7b46b9.
- Is there a fix for CVE-2026-98296?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-98296 attacked?
- It is in an operating system.
- Am I affected by CVE-2026-98296?
- Check whether you run Linux at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The btintel_pcie_prepare_tx() function performs an unchecked memcpy() of skb->len bytes into a fixed 4096-byte DMA buffer. While btintel_pcie_send_frame() validated packet size, direct callers of btintel_pcie_send_sync() could bypass this check. The fix adds length validation in btintel_pcie_send_sync() before the DMA copy, returning -EMSGSIZE for oversized packets.
Affected products
- Linux Kernels with btintel_pcie driver prior to commit 4b837ebd0ea21ae5cc26f02dc042edc6fe7b46b9
Timeline
- 2026-10-06: disclosed