CVE-2026-23069
Integer Underflow in Linux Kernel vsock virtio Credit Calculation
Publication date: 2026-02-04
Last updated on: 2026-03-13
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.2 (inc) to 6.6.122 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.68 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.18.8 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 4.8 (inc) to 6.1.162 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-191 | The product subtracts one value from another, such that the result is less than the minimum allowable integer value, which produces a value that is not equal to the correct result. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's vsock/virtio component, specifically in the function virtio_transport_get_credit(). The function calculates credits using unsigned arithmetic, which can lead to an underflow when the peer reduces its advertised buffer size while data is still in transit. This underflow causes the calculation to produce a large positive value, potentially allowing more data to be queued than the peer can handle.
The issue is fixed by reusing the function virtio_transport_has_space(), which already handles this case correctly, and by adding comments to clarify the reasoning.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing more data to be queued than the peer system can handle. This could potentially lead to resource exhaustion or unexpected behavior in communication between virtual sockets, possibly causing performance degradation or instability in systems relying on the affected Linux kernel component.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been resolved by fixing the potential underflow in the Linux kernel's virtio_transport_get_credit() function.
To mitigate this vulnerability, update your Linux kernel to a version that includes the fix where virtio_transport_has_space() is used instead of duplicating the vulnerable code.