Answer in brief
CVE-2025-39718 records a Unknown severity vulnerability in vsock/virtio: Validate length in packet header before skb_put(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=baddcc2c71572968cdaeee1c4ab3dc0ad90fa765 <969b06bd8b7560efb100a34227619e7d318fbe05 || >=71dc9ec9ac7d3eee785cdc986c3daeb821381e20 <ee438c492b2e0705d819ac0e25d04fae758d8f8f || >=71dc9ec9ac7d3eee785cdc986c3daeb821381e20 <faf332a10372390ce65d0b803888f4b25a388335 || >=71dc9ec9ac7d3eee785cdc986c3daeb821381e20 <676f03760ca1d69c2470cef36c44dc152494b47c || >=71dc9ec9ac7d3eee785cdc986c3daeb821381e20 <0dab92484474587b82e8e0455839eaf5ac7bf894 || >=6.1.63 <6.1.149 | 969b06bd8b7560efb100a34227619e7d318fbe05, ee438c492b2e0705d819ac0e25d04fae758d8f8f, faf332a10372390ce65d0b803888f4b25a388335, 676f03760ca1d69c2470cef36c44dc152494b47c, 0dab92484474587b82e8e0455839eaf5ac7bf894, 6.1.149 |
| Linux/Linuxgeneric | 6.3 | Not reported |
| Siemens/SIMATIC CN 4100generic | >=0 <V5.0 | V5.0 |
Published upstream
Sep 5, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: Validate length in packet header before skb_put() When receiving a vsock packet in the guest, only the virtqueue buffer size is validated prior to virtio_vsock_skb_rx_put(). Unfortunately, virtio_vsock_skb_rx_put() uses the length from the packet header as the length argument to skb_put(), potentially resulting in SKB overflow if the host has gone wonky. Validate the length as advertised by the packet header before calling virtio_vsock_skb_rx_put().
Quoted source text, attributed separately from HOL analysis.