CVE-2026-99027 json
net: team: stop reusing skb after queue override
published 19d ago modified 12d ago also EUVD-2026-108822
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
net: team: stop reusing skb after queue override
A nonzero dev_queue_xmit() result does not return ownership of the skb. When an override port's qdisc drops it, the queue override helper used to try another port or the mode transmit op with the freed skb.
Return the handoff decision separately from transmit success. Select only the first override port under RCU and stop after handing it the skb, regardless of the lower transmit result. Keep the existing success and drop accounting.
BUG: KASAN: slab-use-after-free in sk_skb_reason_drop Write of size 4 by task poc/5040 sk_skb_reason_drop (net/core/skbuff.c:1240) dev_kfree_skb_any_reason (net/core/dev.c:3470) ab_transmit (drivers/net/team/team_mode_activebackup.c:49) team_xmit (drivers/net/team/team_core.c:1849) __dev_direct_xmit (net/core/dev.c:4934) Freed by task 5040: __tcf_kfree_skb_list (net/sched/sch_generic.c:43) __dev_queue_xmit (net/core/dev.c:4831) team_xmit (drivers/net/team/team_core.c:1846) Kernel panic - not syncing: KASAN: panic_on_warn set ...
Patch / fix
- Linux Linux 7.3
- linux Debian 13 6.12.115-2
- linux Debian 14 7.2.11-1
debian advisories DEBIAN-CVE-2026-99027
- linux Ubuntu 26.10 7.3.0-10.10
- linux-aws Ubuntu 26.10 7.3.0-1004.4
- linux-gcp Ubuntu 26.10 7.3.0-1004.4
- linux-raspi Ubuntu 26.10 7.3.0-1004.4
- linux-riscv Ubuntu 26.10 7.3.0-10.10.1
- linux-oracle Ubuntu 26.10 7.3.0-1004.4
- linux-realtime Ubuntu 26.10 7.3.0-10.10.1
ubuntu advisories UBUNTU-CVE-2026-99027
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/13be794844e368b4f8e8d33e97efa23c0a1ebaf8 commit
- git.kernel.org/stable/c/e40846f661075c4c653988363f38e6868bd0a240 commit
- git.kernel.org/stable/c/eaf49fba9cd054e84906d2416e8662194f763c9e commit
- git.kernel.org/stable/c/b21f20320fa2f3c683e3334d70de6bfd172e544a commit
- git.kernel.org/stable/c/07a48cfceb3d0555710a9acb87c949500a7b4523 commit
- git.kernel.org/stable/c/0c0568c9d35c47dc8e3ef6705d4c35a02bd88c4e commit
- git.kernel.org/stable/c/bed63353341d2d44cbad034001dd382cfe3a3892 commit
- git.kernel.org/stable/c/b7454f1940c5e6d92e753853c476a769e452f30a commit
Is CVE-2026-99027 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-99027 updated cvss 5.5
kernel: net: team: stop reusing skb after queue override
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/13be794844e368b4f8e8d33e97efa23c0a1ebaf8
- git.kernel.org /stable/c/e40846f661075c4c653988363f38e6868bd0a240
- git.kernel.org /stable/c/eaf49fba9cd054e84906d2416e8662194f763c9e
- git.kernel.org /stable/c/b21f20320fa2f3c683e3334d70de6bfd172e544a
- git.kernel.org /stable/c/07a48cfceb3d0555710a9acb87c949500a7b4523
- git.kernel.org /stable/c/0c0568c9d35c47dc8e3ef6705d4c35a02bd88c4e
- git.kernel.org /stable/c/bed63353341d2d44cbad034001dd382cfe3a3892
- git.kernel.org /stable/c/b7454f1940c5e6d92e753853c476a769e452f30a
Sources
- CVE List CVE-2026-99027
- NVD CVE-2026-99027
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.