Vulnerability in Kernel
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-63869 has been found in Kernel.
Confidential information can be exposed externally. CVSS score: 7.6/10.
What to do: upgrade Kernel to 6.12.94, 6.18.36, 7.0.13 or later.
If unsure, ask your IT team or search "Kernel CVE-2026-63869" on the vendor's site.
CVE-2026-63869 (Kernel) — CWE-190 / CVSS v3 7.6
Attack vector: adjacent-network / no user interaction
Patched: 6.12.94, 6.18.36, 7.0.13 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-190) exists in Kernel.
Check the vendor advisory for the affected versions of Kernel.
Severity: High (CVSS 7.6/10). Confidential information can be exposed externally.
Update to 6.12.94, 6.18.36, 7.0.13.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Kernel' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1
Identify exposureidentify
grep -r 'Kernel' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Kernelを grep し、稼働しているサービス・バージョンを把握する。 -
2
Apply patchpatch
Upgrade Kernel to 6.12.94, 6.18.36, 7.0.13ステージング環境で 6.12.94, 6.18.36, 7.0.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3
Post-deployment verificationverify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| Linux | Kernel |
≥ 6.7.0, < 6.12.94 ≥ 6.13.0, < 6.18.36 ≥ 6.19.0, < 7.0.13 |
6.12.94 6.18.36 7.0.13 |
Fix status by distribution
Fixed packages published by each distribution for this CVE
- BellSoft Alpaquita BELL-CVE-2026-63869 linux-lts Fixed in: 6.12.95-r0
- Debian DEBIAN-CVE-2026-63869 linux Fixed in: 6.12.94-1
- Ubuntu UBUNTU-CVE-2026-63869 linux-hwe-edge
Original description The description as published by the source.
In the Linux kernel, the following vulnerability has been resolved:
wifi: mac80211: limit injected antenna index in ieee80211_parse_tx_radiotap
When parsing the radiotap header of an injected frame,
ieee80211_parse_tx_radiotap() uses the IEEE80211_RADIOTAP_ANTENNA value
directly as a shift count:
info->control.antennas |= BIT(*iterator.this_arg);
*iterator.this_arg is an 8-bit value taken straight from the frame
supplied by userspace, so BIT() can be asked to shift by up to 255. That
is undefined behaviour on the unsigned long and is reported by UBSAN:
UBSAN: shift-out-of-bounds in net/mac80211/tx.c:2174:30
shift exponent 235 is too large for 64-bit type 'unsigned long'
Call Trace:
ieee80211_parse_tx_radiotap+0xadb/0x1950 net/mac80211/tx.c:2174
ieee80211_monitor_start_xmit+0xb1f/0x1250 net/mac80211/tx.c:2451
...
packet_sendmsg+0x3eb6/0x50f0 net/packet/af_packet.c:3109
info->control.antennas is a 2-bit bitmap (u8 antennas:2), so only antenna
indices 0 and 1 can ever be represented. Ignore any larger value instead
of shifting out of bounds.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
References
- advisory github.com
- package git.kernel.org
- web nvd.nist.gov
- web git.kernel.org
- web git.kernel.org
- web git.kernel.org
- web git.kernel.org
- web github.com