CVE-2026-23280 | Linux Kernel up to 6.18.16/6.19.6/7.0-rc1 amdxdna check_add_overflow memory corruption

VDB-352998 · CVE-2026-23280 · GCVE-0-2026-23280 LINUX KERNEL UP TO 6.18.16/6.19.6/7.0-RC1 AMDXDNA CHECK_ADD_OVERFLOW MEMORY CORRUPTION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 7.6 $5k-$25k 2.83+ Summaryinfo A vulnerability, which was classified as critical, was found in Linux Kernel up to 6.18.16/6.19.6/7.0-rc1. This affects the function check_add_overflow of the component amdxdna. The manipulation results in memory corruption. This vulnerability was named CVE-2026-23280. There is no available exploit. You should upgrade the affected component. Detailsinfo A vulnerability classified as critical has been found in Linux Kernel up to 6.18.16/6.19.6/7.0-rc1. Affected is the function check_add_overflow of the component amdxdna. 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. CVE summarizes: In the Linux kernel, the following vulnerability has been resolved: accel/amdxdna: Prevent ubuf size overflow The ubuf size calculation may overflow, resulting in an undersized allocation and possible memory corruption. Use check_add_overflow() helpers to validate the size calculation before allocation. The advisory is available at git.kernel.org. This vulnerability is traded as CVE-2026-23280 since 01/13/2026. The exploitability is told to be easy. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 03/25/2026). Upgrading to version 6.18.17, 6.19.7 or 7.0-rc2 eliminates this vulnerability. Applying the patch 1500b31db94374a6669e73ce94d6f71cf8e85e06/972bf4a23478fcb247b4f507d47a584bc8aea5bd/03808abb1d868aed7478a11a82e5bb4b3f1ca6d6 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 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 6.18.10 6.18.11 6.18.12 6.18.13 6.18.14 6.18.15 6.18.16 6.19.0 6.19.1 6.19.2 6.19.3 6.19.4 6.19.5 6.19.6 7.0-rc1 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 6.18.17/6.19.7/7.0-rc2 Patch: 1500b31db94374a6669e73ce94d6f71cf8e85e06/972bf4a23478fcb247b4f507d47a584bc8aea5bd/03808abb1d868aed7478a11a82e5bb4b3f1ca6d6 Timelineinfo 01/13/2026 CVE reserved 03/25/2026 +71 days Advisory disclosed 03/25/2026 +0 days VulDB entry created 03/25/2026 +0 days VulDB entry last update Sourcesinfo Vendor: kernel.org Advisory: git.kernel.org Status: Confirmed CVE: CVE-2026-23280 (🔒) GCVE (CVE): GCVE-0-2026-23280 GCVE (VulDB): GCVE-100-352998 Entryinfo Created: 03/25/2026 12:05 Changes: 03/25/2026 12:05 (59) Complete: 🔍 Cache ID: 99:120:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸