CVE-2026-63870 json
ieee802154: 6lowpan: only accept IPv6 packets in lowpan_xmit()
published 3mo ago modified 16d ago also EUVD-2026-45555
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
ieee802154: 6lowpan: only accept IPv6 packets in lowpan_xmit()
The aoe driver (or similar) generates a non-IPv6 packet (e.g., ETH_P_AOE) and queues it for transmission via dev_queue_xmit() on a 6LoWPAN interface (configured by the user or test case).
Since the packet is not IPv6, the 6LoWPAN header_ops->create function (lowpan_header_create or header_create) returns early without initializing the lowpan_addr_info structure in the skb headroom.
In the transmit function (lowpan_xmit), the driver calls lowpan_header (or setup_header) which unconditionally copies and uses the lowpan_addr_info from the headroom, which contains uninitialized data.
Fix this by dropping non IPv6 packets.
A similar fix is needed in net/bluetooth/6lowpan.c bt_xmit().
Patch / fix
- Linux Linux 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, 6.18.36, 7.0.13, 7.1
- linux Debian 12 6.1.176-1
- linux Debian 13 6.12.94-1
- linux Debian 14 7.0.13-1
debian advisories DEBIAN-CVE-2026-63870
- linux Ubuntu 22.04 LTS 5.15.0-198.208
- linux Ubuntu 24.04 LTS 6.8.0-146.146
- linux Ubuntu 26.04 LTS 7.0.0-31.31
- linux-aws Ubuntu 22.04 LTS 5.15.0-1117.124
- linux-aws Ubuntu 24.04 LTS 6.8.0-1066.69
- linux-aws Ubuntu 26.04 LTS 7.0.0-1012.12
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1118.128
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1070.78
ubuntu advisories UBUNTU-CVE-2026-63870
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/af07fffbd53ddc3ec3c2a4ca914f27899fa89bca commit
- git.kernel.org/stable/c/3150e6d3223dfc356308125cabf9c34169842d2a commit
- git.kernel.org/stable/c/8da95cb6ad7d656c871e776a9c7b77e894d6d89c commit
- git.kernel.org/stable/c/1a827b95e62b4cbe851ae7cc9c961cdfa769cca4 commit
- git.kernel.org/stable/c/c1819c8defa235c7beda859bc185b1c429a55ecd commit
- git.kernel.org/stable/c/285b0842f2e01c3edf805f1fd64da11d9b7f6b4c commit
- git.kernel.org/stable/c/87172cc8dc49aaf54407a31edffb0232f8cb93ab commit
- git.kernel.org/stable/c/3a5f3f7aff18bcc36a57839cf50cf0cc8de707f3 commit
Is CVE-2026-63870 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-63870 updated cvss 6.1
kernel: ieee802154: 6lowpan: only accept IPv6 packets in lowpan_xmit()
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: workaround, 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 10 kernelnot 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
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 26d ago
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
- Technology feeds
References
-
git.kernel.org
/stable/c/af07fffbd53ddc3ec3c2a4ca914f27899fa89bca
patch
-
git.kernel.org
/stable/c/3150e6d3223dfc356308125cabf9c34169842d2a
patch
-
git.kernel.org
/stable/c/8da95cb6ad7d656c871e776a9c7b77e894d6d89c
patch
-
git.kernel.org
/stable/c/1a827b95e62b4cbe851ae7cc9c961cdfa769cca4
patch
-
git.kernel.org
/stable/c/c1819c8defa235c7beda859bc185b1c429a55ecd
patch
-
git.kernel.org
/stable/c/285b0842f2e01c3edf805f1fd64da11d9b7f6b4c
patch
-
git.kernel.org
/stable/c/87172cc8dc49aaf54407a31edffb0232f8cb93ab
patch
-
git.kernel.org
/stable/c/3a5f3f7aff18bcc36a57839cf50cf0cc8de707f3
patch
Sources
- CVE List CVE-2026-63870
- NVD CVE-2026-63870
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.