CVE-2026-90055: usb: atm: usbatm: fix invalid ci_range initialization
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 1e964d414bfd9f8dfe9948d08e4b9dda4ed2e422, 561cbd6d49022c9a383e22a39c87a165a4d39f9c, 75667703115154a4fd9cf259d4f826d8729cbcda.
Low priority for now. Upgrade to Linux Linux 1e964d414bfd9f8dfe9948d08e4b9dda4ed2e422, 561cbd6d49022c9a383e22a39c87a165a4d39f9c, 75667703115154a4fd9cf259d4f826d8729cbcda or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: usb: atm: usbatm: fix invalid ci_range initialization syzbot reported a shift-out-of-bounds in __vcc_connect(): UBSAN: shift-out-of-bounds in net/atm/common.c:382:32 shift exponent -1 is negative CPU: 0 UID: 0 PID: 5987 Comm: syz.0.18 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 08/05/2026 Call Trace: <TASK> dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 ubsan_epilogue+0xa/0x30 lib/ubsan.c:233 __ubsan_handle_shift_out_of_bounds+0x36d/0x400 lib/ubsan.c:494 __vcc_connect+0x14b4/0x19c0 net/atm/common.c:382 vcc_connect+0x328/0x8f0 net/atm/common.c:498 pvc_bind+0x272/0x380 net/atm/pvc.c:52 __sys_bind+0x2e3/0x410 net/socket.c:1976 __x64_sys_bind+0x7a/0x90 net/socket.c:1979 ... ATM device ci_range fields (vpi_bits and vci_bits) represent the number of bits supported for VPI and VCI addressing on the device. net/atm/common.c directly uses these fields as bit shift counts: vpi >> dev->ci_range.vpi_bits vci >> dev->ci_range.vci_bits 1 << vcc->dev->ci_range.vpi_bits 1 << vcc->dev->ci_range.vci_bits usbatm_atm_init() sets ci_range.vpi_bits and ci_range.vci_bits to ATM_CI_MAX (-1), which is defined in <uapi/linux/atmdev.h> as a sentinel value for userspace ATM_SETCIRANGE requests, not a valid bit count. Shifting by -1 is undefined behavior and triggers UBSAN warnings. ATM UNI cell headers allow up to 8 bits for VPI (0..255) and 16 bits for VCI (0..65535). Initialize vpi_bits to 8 and vci_bits to 16, as done by solos-pci.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.13affected
- c59bba75fa500f13ef14215d599ee0d7faa1b954 and later · before 8442586526c406527bf31206e538c0ce6bc672e6affected · git
- c59bba75fa500f13ef14215d599ee0d7faa1b954 and later · before 561cbd6d49022c9a383e22a39c87a165a4d39f9caffected · git
- c59bba75fa500f13ef14215d599ee0d7faa1b954 and later · before 76bc7c3a44856744b64aa91d9afe6d9522a78c42affected · git
- c59bba75fa500f13ef14215d599ee0d7faa1b954 and later · before 7baa0c92be39eb3da755ed6f200497a57078c47baffected · git
- c59bba75fa500f13ef14215d599ee0d7faa1b954 and later · before 1e964d414bfd9f8dfe9948d08e4b9dda4ed2e422affected · git
- c59bba75fa500f13ef14215d599ee0d7faa1b954 and later · before ff7f77a234f7b74e5955a6e34fa74eca4c9ca44caffected · git
- c59bba75fa500f13ef14215d599ee0d7faa1b954 and later · before 75667703115154a4fd9cf259d4f826d8729cbcdaaffected · git
- c59bba75fa500f13ef14215d599ee0d7faa1b954 and later · before a60fd8c6dbaa76da4163cf225ed2b9e982540f39affected · git
- before 2.6.13not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90053Sep 17, 2026 · net/sched: sch_htb: limit htb_classify inner-class filter hops0Monitor
- ← EarlierCVE-2026-90054Sep 17, 2026 · tcp: fix corruption of urgent data on multi-segment retransmit0Monitor
- Later →CVE-2026-90056Sep 17, 2026 · net: fec: only stop PTP if it was initialized0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1e964d414bfd9f8dfe9948d08e4b9dda4ed2e422 | Vendor (CNA) |
| Linux Linux | 561cbd6d49022c9a383e22a39c87a165a4d39f9c | Vendor (CNA) |
| Linux Linux | 75667703115154a4fd9cf259d4f826d8729cbcda | Vendor (CNA) |
| Linux Linux | 76bc7c3a44856744b64aa91d9afe6d9522a78c42 | Vendor (CNA) |
| Linux Linux | 7baa0c92be39eb3da755ed6f200497a57078c47b | Vendor (CNA) |
| Linux Linux | 8442586526c406527bf31206e538c0ce6bc672e6 | Vendor (CNA) |
| Linux Linux | a60fd8c6dbaa76da4163cf225ed2b9e982540f39 | Vendor (CNA) |
| Linux Linux | ff7f77a234f7b74e5955a6e34fa74eca4c9ca44c | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/561cbd6d49022c9a383e22a39c87a165a4d39f9c
- git.kernel.org/stable/c/75667703115154a4fd9cf259d4f826d8729cbcda
- git.kernel.org/stable/c/76bc7c3a44856744b64aa91d9afe6d9522a78c42
- git.kernel.org/stable/c/7baa0c92be39eb3da755ed6f200497a57078c47b
- git.kernel.org/stable/c/8442586526c406527bf31206e538c0ce6bc672e6
- git.kernel.org/stable/c/a60fd8c6dbaa76da4163cf225ed2b9e982540f39
- git.kernel.org/stable/c/ff7f77a234f7b74e5955a6e34fa74eca4c9ca44c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.