Vulnerability · Published Feb 4, 2026 · Assigned by Linux
CVE-2026-23069vsock/virtio: fix potential underflow in virtio_transport_get_credit()
Medium 5.5
In plain English
A medium-severity integer overflow in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 8% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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]
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.1.162-1 | DEBIAN-CVE-2026-23069 |
| Debian:13 | linux | 6.12.69-1 | DEBIAN-CVE-2026-23069 |
| Debian:14 | linux | 6.18.8-1 | DEBIAN-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux | 6.8.0-117.117 | UBUNTU-CVE-2026-23069 |
| Ubuntu:25.10 | linux | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-aws | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1055.58 | UBUNTU-CVE-2026-23069 |
| Ubuntu:25.10 | linux-aws | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-aws-6.14 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-aws-6.17 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1057.60~22.04.1 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-azure | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1056.62 | UBUNTU-CVE-2026-23069 |
| Ubuntu:25.10 | linux-azure | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-azure-6.14 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-azure-6.17 | 6.17.0-1021.21~24.04.1 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1059.65~22.04.1 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-azure-fde | 6.8.0-1058.65 | UBUNTU-CVE-2026-23069 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-azure-fde-6.14 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1058.65~22.04.1 | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-azure-nvidia-6.14 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-gcp | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1058.61 | UBUNTU-CVE-2026-23069 |
| Ubuntu:25.10 | linux-gcp | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-gcp-6.14 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-gcp-6.17 | 6.17.0-1021.24~24.04.1 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1060.63~22.04.1 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-gke | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1054.60 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-gkeop | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1041.44 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-hwe-6.14 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-hwe-6.17 | 6.17.0-41.41~24.04.1 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-124.124~22.04.1 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-ibm | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1055.56 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1055.56~22.04.1 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-intel-iotg | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-kvm | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-lowlatency | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-117.117.1 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-117.117.1~22.04.1 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1054.57 | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-nvidia-6.17 | 6.17.0-1031.31 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1054.57~22.04.1 | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1054.57.1 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1024.24 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-oem-6.14 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-oem-6.17 | 6.17.0-1030.30 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-oracle | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1054.55 | UBUNTU-CVE-2026-23069 |
| Ubuntu:25.10 | linux-oracle | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-oracle-6.14 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-oracle-6.17 | 6.17.0-1019.19~24.04.3 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1054.55~22.04.1 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1056.60 | UBUNTU-CVE-2026-23069 |
| Ubuntu:25.10 | linux-raspi | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:25.10 | linux-realtime | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:25.10 | linux-riscv | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-riscv-6.14 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-riscv-6.17 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-117.117~22.04.1 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2026-23069 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1032.33 | UBUNTU-CVE-2026-23069 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | no fix listed | UBUNTU-CVE-2026-23069 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 06a8fc78367d070720af960dcecec917d3ae5f3b – before d96de882d6b99955604669d962ae14e94b66a55106a8fc78367d070720af960dcecec917d3ae5f3b – before 02f9af192b98d15883c70dd41ac76d1b0217c89906a8fc78367d070720af960dcecec917d3ae5f3b – before d05bc313788f0684b27f0f5b60c52a844669b54206a8fc78367d070720af960dcecec917d3ae5f3b – before ec0f1b3da8061be3173d1c39faaf9504f91942c306a8fc78367d070720af960dcecec917d3ae5f3b – before 3ef3d52a1a9860d094395c7a3e593f3aa26ff012 |
| Linux | Linux | 4.8 |
Weakness: CWE-190
References
- https://git.kernel.org/stable/c/d96de882d6b99955604669d962ae14e94b66a551
- https://git.kernel.org/stable/c/02f9af192b98d15883c70dd41ac76d1b0217c899
- https://git.kernel.org/stable/c/d05bc313788f0684b27f0f5b60c52a844669b542
- https://git.kernel.org/stable/c/ec0f1b3da8061be3173d1c39faaf9504f91942c3
- https://git.kernel.org/stable/c/3ef3d52a1a9860d094395c7a3e593f3aa26ff012