CVE-2026-23262 | Linux Kernel up to 6.18.9 gve memory corruption

VDB-351579 · CVE-2026-23262 · GCVE-0-2026-23262 LINUX KERNEL UP TO 6.18.9 GVE MEMORY CORRUPTION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 7.6 $5k-$25k 0.50+ Summaryinfo A vulnerability marked as critical has been reported in Linux Kernel up to 6.18.9. This affects an unknown function of the component gve. Performing a manipulation results in memory corruption. This vulnerability is cataloged as CVE-2026-23262. There is no exploit available. It is suggested to upgrade the affected component. Detailsinfo A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.18.9. This affects an unknown code of the component gve. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is: In the Linux kernel, the following vulnerability has been resolved: gve: Fix stats report corruption on queue count change The driver and the NIC share a region in memory for stats reporting. The NIC calculates its offset into this region based on the total size of the stats region and the size of the NIC's stats. When the number of queues is changed, the driver's stats region is resized. If the queue count is increased, the NIC can write past the end of the allocated stats region, causing memory corruption. If the queue count is decreased, there is a gap between the driver and NIC stats, leading to incorrect stats reporting. This change fixes the issue by allocating stats region with maximum size, and the offset calculation for NIC stats is changed to match with the calculation of the NIC. It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-23262 since 01/13/2026. The exploitability is told to be easy. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 03/18/2026). Upgrading to version 5.10.250, 5.15.200, 6.1.163, 6.6.124, 6.12.70 or 6.18.10 eliminates this vulnerability. Applying the patch f432f7613c220db32c2c6942420daf7b3f2e7d7e/9d93332397405b62a3300b22d04ac65d990b91ff/837c662f47dac43efa1aef2dd433c6b4b4c073af/df54838ab61826ecc1a562ffa5e280c3ab7289a7/9fa0a755db3e1945fe00f73fe27d85ef6c8818b7/11f8311f69e4c361717371b4901ff92daeb76e9c/7b9ebcce0296e104a0d82a6b09d68564806158ff 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. Productinfo Type Operating System Vendor Linux Name Kernel Version 5.10.249 5.15.199 6.1.162 6.6.123 6.12.0 6.12.1 6.12.2 6.12.3 6.12.4 6.12.5 6.12.6 6.12.7 6.12.8 6.12.9 6.12.10 6.12.11 6.12.12 6.12.13 6.12.14 6.12.15 6.12.16 6.12.17 6.12.18 6.12.19 6.12.20 6.12.21 6.12.22 6.12.23 6.12.24 6.12.25 6.12.26 6.12.27 6.12.28 6.12.29 6.12.30 6.12.31 6.12.32 6.12.33 6.12.34 6.12.35 6.12.36 6.12.37 6.12.38 6.12.39 6.12.40 6.12.41 6.12.42 6.12.43 6.12.44 6.12.45 6.12.46 6.12.47 6.12.48 6.12.49 6.12.50 6.12.51 6.12.52 6.12.53 6.12.54 6.12.55 6.12.56 6.12.57 6.12.58 6.12.59 6.12.60 6.12.61 6.12.62 6.12.63 6.12.64 6.12.65 6.12.66 6.12.67 6.12.68 6.12.69 6.18.0 6.18.1 6.18.2 6.18.3 6.18.4 6.18.5 6.18.6 6.18.7 6.18.8 6.18.9 License open-source Website Vendor: https://www.kernel.org/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 8.0 VulDB Meta Temp Score: 7.6 VulDB Base Score: 8.0 VulDB Temp Score: 7.6 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Memory corruption CWE: CWE-119 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Partially Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: Kernel 5.10.250/5.15.200/6.1.163/6.6.124/6.12.70/6.18.10 Patch: f432f7613c220db32c2c6942420daf7b3f2e7d7e/9d93332397405b62a3300b22d04ac65d990b91ff/837c662f47dac43efa1aef2dd433c6b4b4c073af/df54838ab61826ecc1a562ffa5e280c3ab7289a7/9fa0a755db3e1945fe00f73fe27d85ef6c8818b7/11f8311f69e4c361717371b4901ff92daeb76e9c/7b9ebcce0296e104a0d82a6b09d68564806158ff Timelineinfo 01/13/2026 CVE reserved 03/18/2026 +64 days Advisory disclosed 03/18/2026 +0 days VulDB entry created 03/18/2026 +0 days VulDB entry last update Sourcesinfo Vendor: kernel.org Advisory: git.kernel.org Status: Confirmed CVE: CVE-2026-23262 (🔒) GCVE (CVE): GCVE-0-2026-23262 GCVE (VulDB): GCVE-100-351579 Entryinfo Created: 03/18/2026 19:52 Changes: 03/18/2026 19:52 (58) Complete: 🔍 Cache ID: 99:6D9:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸