CVE-2024-50169
vsock: Update rx_bytes on read_skb()
No known exploitation. EPSS puts it in the 11th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 634f1a7110b439c65fd8a809171c1d2d28bcea6f, < 66cd51de31c682a311c2fa25c580b7ea45859dd9Upgrade to: 66cd51de31c682a311c2fa25c580b7ea45859dd9Affected: ≥ 634f1a7110b439c65fd8a809171c1d2d28bcea6f, < e5ca2b98090b4bb1c393088c724af6c37812a829Upgrade to: e5ca2b98090b4bb1c393088c724af6c37812a829Affected: ≥ 634f1a7110b439c65fd8a809171c1d2d28bcea6f, < 3543152f2d330141d9394d28855cb90b860091d2Upgrade to: 3543152f2d330141d9394d28855cb90b860091d2Stated by: CVE record
- Сообщество свободного программного обеспечения Debian GNU/LinuxAffected: 11Upgrade to: not statedStated by: BDU
- ООО «РусБИТех-Астра» Astra Linux Special EditionAffected: 1.8Upgrade to: not statedStated by: BDU
- АО «НППКТ» ОСОН ОСнова ОnyxAffected: до 2.12Upgrade to: not statedStated by: BDU
- Сообщество свободного программного обеспечения LinuxAffected: от 6.7 до 6.11.6Upgrade to: not statedStated by: BDU
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: vsock: Update rx_bytes on read_skb() Make sure virtio_transport_inc_rx_pkt() and virtio_transport_dec_rx_pkt() calls are balanced (i.e. virtio_vsock_sock::rx_bytes doesn't lie) after vsock_transport::read_skb(). While here, also inform the peer that we've freed up space and it has more credit. Failing to update rx_bytes after packet is dequeued leads to a warning on SOCK_STREAM recv(): [ 233.396654] rx_queue is empty, but rx_bytes is non-zero [ 233.396702] WARNING: CPU: 11 PID: 40601 at net/vmw_vsock/virtio_transport_common.c:589
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 11th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
5 events over 595 days, from the signal feeds we watch.
- OpenVAS check added
- Patch availablerecord updated
- Publishedweakness classified
Affected products
And 1 more affected product. See all after sign-in
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Scored 5.5 by NVD.
How it is reached
- Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required LowRequires basic user-level privileges
- User Interaction NoneNo user interaction needed — fully automated exploitation
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality NoneNo confidentiality impact
- Integrity NoneNo integrity impact
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Debian GNU/Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI