CVE-2026-23069: Linux kernel · vsock/virtio: fix potential underflow in virtio_transport_get_credit()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ec0f1b3da8061be3173d1c39faaf9504f91942c3 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 10:24 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-06-10.
- Patch
- Available – fixed in ec0f1b3da8061be3173d1c39faaf9504f91942c3, d96de882d6b99955604669d962ae14e94b66a551, d05bc313788f0684b27f0f5b60c52a844669b542 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 4 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: fix potential underflow in virtio_transport_get_credit() The credit calculation in virtio_transport_get_credit() uses unsigned arithmetic: ret = vvs->peer_buf_alloc - (vvs->tx_cnt - vvs->peer_fwd_cnt); If the peer shrinks its advertised buffer (peer_buf_alloc) while bytes are in flight, the subtraction can underflow and produce a large positive value, potentially allowing more data to be queued than the peer can handle. Reuse virtio_transport_has_space() which already handles this case and add a comment to make it clear why we are doing that. [Stefano: use virtio_transport_has_space() instead of duplicating the code] [Stefano: tweak the commit message]
References
- git.kernel.org/stable/c/d96de882d6b99955604669d962ae14e94b66a551 (opens in a new tab)
- git.kernel.org/stable/c/02f9af192b98d15883c70dd41ac76d1b0217c899 (opens in a new tab)
- git.kernel.org/stable/c/d05bc313788f0684b27f0f5b60c52a844669b542 (opens in a new tab)
- git.kernel.org/stable/c/ec0f1b3da8061be3173d1c39faaf9504f91942c3 (opens in a new tab)
- git.kernel.org/stable/c/3ef3d52a1a9860d094395c7a3e593f3aa26ff012 (opens in a new tab)