CVE-2026-90138: vsock: don't check the listener's sk_err in vsock_accept()
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 36e5fa009f98a4edbe1783ac11c0df672b224742, 491b368a0c6e5f28b615a50b0d384f5c25fde2a7, 64348c55dd7596ca2c033dcd102af44bdd7e8acd.
Low priority for now. Upgrade to Linux Linux 36e5fa009f98a4edbe1783ac11c0df672b224742, 491b368a0c6e5f28b615a50b0d384f5c25fde2a7, 64348c55dd7596ca2c033dcd102af44bdd7e8acd 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: vsock: don't check the listener's sk_err in vsock_accept() Syzbot reported an issue which can be reproduced with these steps: r0 = socket(AF_VSOCK, SOCK_STREAM, 0) bind(r0, {VMADDR_CID_ANY, PORT}) connect(r0, {VMADDR_CID_LOCAL, PORT}) -> -1, EPROTO (self-connect) listen(r0, backlog) -> 0 r1 = socket(AF_VSOCK, SOCK_STREAM, 0) connect(r1, {VMADDR_CID_LOCAL, PORT}) -> 0 accept(r0) -> -1, EPROTO (stale sk_err) Basically, it creates a socket (r0) and triggers a self-connect after binding it. This self-connect fails with EPROTO because it loops back to r0 while the socket is still in the TCP_SYN_SENT state, causing it to be incorrectly dispatched to the connecting-client path. The unexpected packet type encountered there sets sk_err to EPROTO. After that, it invokes a listen() call on the same socket. This listen() call succeeds because the kernel's listening path never inspects or clears sk_err. Then, a new socket (r1) is created as a normal client and connects to r0. However, vsock_accept() rejects this incoming connection because the listener's sk_err still holds the EPROTO error from the earlier failed self-connect. This rejection causes the child socket created for r1's connection to never be freed on virtio or hyperv transports; only the VMCI transport implements pending_work to revisit and clean up a rejected socket. For a non-blocking connect(), vsock_connect() may return -EINPROGRESS immediately, and vsock_connect_timeout() can later set sk->sk_err asynchronously. Since no vsock transport ever sets sk_err on a socket while it is in TCP_LISTEN state, checking it in vsock_accept() serves no purpose and only carries forward errors left behind by earlier, unrelated connection attempts on the same socket. Remove the checks so accept() no longer rejects valid incoming connections because of a stale error, which also avoids the resource leak described above.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th 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
- 3.9affected
- d021c344051af91f42c5ba9fdedc176740cbd238 and later · before c99d12052f663d9914bc944302fee5a1d50d8ca5affected · git
- d021c344051af91f42c5ba9fdedc176740cbd238 and later · before 64348c55dd7596ca2c033dcd102af44bdd7e8acdaffected · git
- d021c344051af91f42c5ba9fdedc176740cbd238 and later · before c5a75d37c21e558cc6fad1597e732ead30745eedaffected · git
- d021c344051af91f42c5ba9fdedc176740cbd238 and later · before 36e5fa009f98a4edbe1783ac11c0df672b224742affected · git
- d021c344051af91f42c5ba9fdedc176740cbd238 and later · before 491b368a0c6e5f28b615a50b0d384f5c25fde2a7affected · git
- d021c344051af91f42c5ba9fdedc176740cbd238 and later · before b8c899cf5e7be29840a172c183dedd8d3e7a0287affected · git
- before 3.9not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not 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 | from 0 | — |
| 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-90136Sep 17, 2026 · platform/x86/amd/hsmp: Reject negative power cap writes in hwmon0Monitor
- ← EarlierCVE-2026-90137Sep 17, 2026 · platform/x86: hp-bioscfg: fix password encoding bounds check30Monitor
- Later →CVE-2026-90139Sep 17, 2026 · fuse: check for NULL root inode in fuse_fill_super_submount0Monitor
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 | 36e5fa009f98a4edbe1783ac11c0df672b224742 | Vendor (CNA) |
| Linux Linux | 491b368a0c6e5f28b615a50b0d384f5c25fde2a7 | Vendor (CNA) |
| Linux Linux | 64348c55dd7596ca2c033dcd102af44bdd7e8acd | Vendor (CNA) |
| Linux Linux | b8c899cf5e7be29840a172c183dedd8d3e7a0287 | Vendor (CNA) |
| Linux Linux | c5a75d37c21e558cc6fad1597e732ead30745eed | Vendor (CNA) |
| Linux Linux | c99d12052f663d9914bc944302fee5a1d50d8ca5 | Vendor (CNA) |
| 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 (5 more)Show less
- git.kernel.org/stable/c/491b368a0c6e5f28b615a50b0d384f5c25fde2a7
- git.kernel.org/stable/c/64348c55dd7596ca2c033dcd102af44bdd7e8acd
- git.kernel.org/stable/c/b8c899cf5e7be29840a172c183dedd8d3e7a0287
- git.kernel.org/stable/c/c5a75d37c21e558cc6fad1597e732ead30745eed
- git.kernel.org/stable/c/c99d12052f663d9914bc944302fee5a1d50d8ca5
Vendor advisories and official records. Exploit/PoC links are deliberately left out.