Look up another CVE · open CVE-2026-68128 in the interactive tracker
CVE-2026-68128
ice: reject out-of-range ptype in ice_parser_profile_init
Published 2026-08-10 (2 months ago) by the Linux kernel CNA. Subsystem drivers/net. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-68128 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | fixed | 6.12.101-1 | Update the kernel and reboot. Fixed in 6.12.101-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.6-1 | Update the kernel and reboot. Fixed in 7.1.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.6-1 | Update the kernel and reboot. Fixed in 7.1.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4745-1 · 2026-08-18 · text | 6.12.101-1~deb12u1 | Update the kernel and reboot. DLA-4745-1 shipped the fix on 2026-08-18, in 6.12.101-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
set_bit(rslt->ptype, prof->ptypes) operates on a DECLARE_BITMAP of ICE_FLOW_PTYPE_MAX (1024) bits. Nothing prevents a malicious VF from providing ptype >= 1024 through VIRTCHNL, resulting in a write past the end of the bitmap and a kernel page fault. Reproduced with a custom kernel module injecting a crafted VIRTCHNL_OP_ADD_RSS_CFG on E810-C QSFP (8086:1592), FW 4.91 0x800214af 1.3909.0, ICE COMMS DDP 1.3.53.0, kernel 7.1.0-rc1. crash_parser: ice_parser_profile_init @ ffffffffc0d61b60 crash_parser: setting ptype=0xffff (max valid=1023) crash_parser: calling ice_parser_profile_init -- expect OOB crash! BUG: kernel NULL pointer dereference, address: 0000000000000000 Oops: Oops: 0002 [#1] SMP NOPTI CPU: 56 UID: 0 PID: 165011 Comm: insmod Kdump: loaded Tainted: G S U OE 7.1.0-rc1 #1 Hardware name: Intel Corporation S2600BPB/S2600BPB RIP: 0010:ice_parser_profile_init+0x2d/0x1d0 [ice] Call Trace: <TASK> ? __pfx_ice_parser_profile_init+0x10/0x10 [ice] crash_init+0x127/0xff0 [crash_parser] do_one_initcall+0x45/0x310 do_init_module+0x64/0x270 init_module_from_file+0xcc/0xf0 idempotent_init_module+0x17b/0x280 __x64_sys_finit_module+0x6e/0xe0 Bail out early with -EINVAL when ptype is out of range.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/net/ethernet/intel/ice/ice_parser.c
- What this is
- INTEL ETHERNET DRIVERSMAINTAINERS section matched on drivers/net/ethernet/intel/*/ · intel-wired-lan@lists.osuosl.org · Maintained
- Kernel module
- ice
Check it on the machine
grep -wE 'CONFIG_ETHERNET|CONFIG_ICE|CONFIG_NET_VENDOR_INTEL' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
lsmod | grep -w icePrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed. The build rule could not be established for 1 release, so nothing is claimed about those.
- bookworm?
- trixieMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armel/rpi
- forky, sid, bookworm · linux-6.12Mnot built on amd64/cloud-amd64, arm64/cloud-arm64
- ?
- not established - no Makefile entry for the affected file
- M
- a module where it is built at all; some flavours do not build it
Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.
- Build switches
- CONFIG_ETHERNET, CONFIG_ICE, CONFIG_NET_VENDOR_INTEL
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-10 (2 months ago)source
- CVSS
- 8.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.14%, higher than 2.9% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/net
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.12 | 6.12.101 | fe2f8d5a77ad |
| 6.12 | 6.18.42 | 5e496f2b615c |
| 6.12 | 7.1.6 | 33cc15aaf249 |
| 6.12 | 7.2 | 59abb87159c5 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4745-1 | 2026-08-18 | bookworm 6.12.101-1~deb12u1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- Exploitation requires a malicious SR-IOV VF (or guest with VF passthrough) to send VIRTCHNL_OP_ADD_RSS_CFG/ADD_FDIR_FILTER mailbox messages to the host PF driver; this is local device/mailbox access, not remote network packet processing.
- AC:LAttack complexity, low
- A VF can craft a raw RSS/FDIR packet pattern that leaves ice_ptype_resolve() returning U16_MAX (0xFFFF); set_bit() then deterministically indexes far past the 1024-bit prof->ptypes bitmap with no attacker-uncontrollable race or layout dependency.
- PR:LPrivileges required, low
- Attack requires control of an assigned E810 VF, typically as a cloud tenant VM with netdev admin capability or a VFIO-delegated process; this is low privilege relative to the host (not init-namespace root), mirroring similar SR-IOV VF bugs.
- UI:NUser interaction, none
- The attacker sends their own VIRTCHNL configuration message (or loads a guest kernel module to do so); no separate victim-user interaction is required beyond routine VF assignment already present in SR-IOV deployments.
- S:CScope, changed
- In virtualized/cloud deployments (the primary E810 use case), a malicious guest VF corrupts host kernel stack memory in the PF driver, crossing the guest-to-host isolation boundary analogous to KVM/SR-IOV escape class bugs.
- C:HConfidentiality impact, high
- The out-of-bounds set_bit() stack write corrupts kernel memory far beyond the 128-byte ptypes bitmap; such uncontrolled memory corruption is leverageable for kernel information disclosure in an exploit chain.
- I:HIntegrity impact, high
- set_bit(0xFFFF, prof->ptypes) performs an arbitrary out-of-bounds stack write (~8 KB past the bitmap on x86_64), providing memory corruption primitives potentially usable for host kernel code execution.
- A:HAvailability impact, high
- The bug was reproduced causing a NULL-pointer kernel oops/page fault in ice_parser_profile_init(); reliable triggering from a malicious VF can panic or lock up the host PF kernel.