CVE-2026-63903 json
USB: serial: belkin_sa: validate interrupt status length
published 3mo ago modified 12d ago also EUVD-2026-45676
- cvss
- 7.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
USB: serial: belkin_sa: validate interrupt status length
The Belkin interrupt callback treats interrupt data as a four-byte status report and reads LSR/MSR fields at offsets 2 and 3. The interrupt-in buffer length is derived from endpoint wMaxPacketSize, and short interrupt transfers may complete successfully with a smaller actual_length.
Check the completed interrupt packet length before parsing status fields so short interrupt endpoints and short successful packets are ignored instead of causing out-of-bounds or stale status-byte reads.
KASAN report as below:
BUG: KASAN: slab-out-of-bounds in belkin_sa_read_int_callback() Read of size 1 Call trace: belkin_sa_read_int_callback() (drivers/usb/serial/belkin_sa.c:202) __usb_hcd_giveback_urb() (drivers/usb/core/hcd.c:1630) dummy_timer() (?:?)
Patch / fix
- Linux Linux 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.93, 6.18.35, 7.0.12, 7.1
- linux Debian 12 6.1.176-1
- linux Debian 13 6.12.94-1
- linux Debian 14 7.0.12-1
debian advisories DEBIAN-CVE-2026-63903
- 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-28.28
- 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-1009.9
- 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-63903
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
- kernel-rt Real Time Module 15 SP7 6.4.0-150700.7.72.1
- kernel-syms-rt Real Time Module 15 SP7 6.4.0-150700.7.72.1
- kernel-source-rt Real Time Module 15 SP7 6.4.0-150700.7.72.1
- kernel-64kb SLE Module for Basesystem 15 SP7 6.4.0-150700.53.78.1
- kernel-syms SLE Module for Development Tools 15 SP7 6.4.0-150700.53.78.1
- kernel-azure SLE Module for Public Cloud 15 SP7 6.4.0-150700.53.78.1
- kernel-source SLE Module for Development Tools 15 SP7, SLE Module for Basesystem 15 SP7 6.4.0-150700.53.78.1
- kernel-default SLE Workstation Extension 15 SP7, SLE Module for Legacy 15 SP7, SLE Module for Basesystem 15 SP7 +2 more 6.4.0-150700.53.78.1
suse advisories SUSE-SU-2026:4687-1SUSE-SU-2026:3810-1SUSE-SU-2026:3790-1SUSE-SU-2026:23244-1SUSE-SU-2026:23241-1SUSE-SU-2026:23194-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.37.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-azure openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.37.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.37.1
opensuse advisories openSUSE-SU-2026:21555-1
- git.kernel.org/stable/c/f1617539ab90e67da788959bfd314076f093a11a commit
- git.kernel.org/stable/c/f361359a952da15e70e693c2d7dca5c5843eae3e commit
- git.kernel.org/stable/c/37e54d1b986df35c936d81e5b59a7aa3ec6938f0 commit
- git.kernel.org/stable/c/ffb739a49186ea784bbd9cb91b647f062395b419 commit
- git.kernel.org/stable/c/6a4602221cba7a738442328d66a2f0b1c9bf6e17 commit
- git.kernel.org/stable/c/22823a319fb2afdf02cacafbed8b613b757efbc8 commit
- git.kernel.org/stable/c/db1e7eb6203d534dad64cac2c793b69e561e657b commit
- git.kernel.org/stable/c/4ce058df2ee02cc2a0f0fd5cd64ce6f1482a0b65 commit
Is CVE-2026-63903 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-63903 updated cvss 5.5
kernel: USB: serial: belkin_sa: validate interrupt status length
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: workaround, no fix planned “Out of support scope”
-
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 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: workaround, no fix available “Fix deferred”
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.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
- Technology feeds
References
-
git.kernel.org
/stable/c/f1617539ab90e67da788959bfd314076f093a11a
patch
-
git.kernel.org
/stable/c/f361359a952da15e70e693c2d7dca5c5843eae3e
patch
-
git.kernel.org
/stable/c/37e54d1b986df35c936d81e5b59a7aa3ec6938f0
patch
-
git.kernel.org
/stable/c/ffb739a49186ea784bbd9cb91b647f062395b419
patch
-
git.kernel.org
/stable/c/6a4602221cba7a738442328d66a2f0b1c9bf6e17
patch
-
git.kernel.org
/stable/c/22823a319fb2afdf02cacafbed8b613b757efbc8
patch
-
git.kernel.org
/stable/c/db1e7eb6203d534dad64cac2c793b69e561e657b
patch
-
git.kernel.org
/stable/c/4ce058df2ee02cc2a0f0fd5cd64ce6f1482a0b65
patch
Sources
- CVE List CVE-2026-63903
- NVD CVE-2026-63903
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.