Linux Kernel up to 6.12.67/6.18.7/6.19-rc6 vsock virtio_vsock_alloc_linear_skb uninitialized pointer

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability categorized as critical has been discovered in Linux Kernel up to 6.12.67/6.18.7/6.19-rc6. This issue affects the function virtio_vsock_alloc_linear_skb of the component vsock. Such manipulation leads to uninitialized pointer. This vulnerability is uniquely identified as CVE-2026-23057. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.12.67/6.18.7/6.19-rc6 and classified as critical. Affected by this issue is the function virtio_vsock_alloc_linear_skb of the component vsock. The manipulation with an unknown input leads to a uninitialized pointer vulnerability. Using CWE to declare the problem leads to CWE-824. The product accesses or uses a pointer that has not been initialized. The impact remains unknown. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: Coalesce only linear skb vsock/virtio common tries to coalesce buffers in rx queue: if a linear skb (with a spare tail room) is followed by a small skb (length limited by GOOD_COPY_LEN = 128), an attempt is made to join them. Since the introduction of MSG_ZEROCOPY support, assumption that a small skb will always be linear is incorrect. In the zerocopy case, data is lost and the linear skb is appended with uninitialized kernel memory. Of all 3 supported virtio-based transports, only loopback-transport is affected. G2H virtio-transport rx queue operates on explicitly linear skbs; see virtio_vsock_alloc_linear_skb() in virtio_vsock_rx_fill(). H2G vhost-transport may allocate non-linear skbs, but only for sizes that are not considered for coalescence; see PAGE_ALLOC_COSTLY_ORDER in virtio_vsock_alloc_skb(). Ensure only linear skbs are coalesced. Note that skb_tailroom(last_skb) > 0 guarantees last_skb is linear.

The advisory is available at git.kernel.org. This vulnerability is handled as CVE-2026-23057 since 01/13/2026. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 04/30/2026).

The vulnerability scanner Nessus provides a plugin with the ID 297868 (Linux Distros Unpatched Vulnerability : CVE-2026-23057), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.12.68, 6.18.8 or 6.19-rc7 eliminates this vulnerability. Applying the patch 568e9cd8ed7ca9bf748c7687ba6501f29d30e59f/63ef9b300bd09e24c57050c5dbe68feedce42e72/0386bd321d0f95d041a7b3d7b07643411b044a96 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (297868) and CERT Bund (WID-SEC-2026-0324). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

  • Debian Linux
  • Google Cloud Platform
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • IBM QRadar SIEM
  • SUSE openSUSE
  • RESF Rocky Linux
  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Uninitialized pointer
CWE: CWE-824 / CWE-908
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 297868
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-23057

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.12.68/6.18.8/6.19-rc7
Patch: 568e9cd8ed7ca9bf748c7687ba6501f29d30e59f/63ef9b300bd09e24c57050c5dbe68feedce42e72/0386bd321d0f95d041a7b3d7b07643411b044a96

Timelineinfo

01/13/2026 CVE reserved
02/04/2026 +22 days Advisory disclosed
02/04/2026 +0 days VulDB entry created
04/30/2026 +85 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-23057 (🔒)
GCVE (CVE): GCVE-0-2026-23057
GCVE (VulDB): GCVE-100-344282
CERT Bund: WID-SEC-2026-0324 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 02/04/2026 17:51
Updated: 04/30/2026 08:26
Changes: 02/04/2026 17:51 (59), 02/06/2026 06:55 (7), 02/08/2026 12:09 (2), 04/30/2026 08:26 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!