CVE-2026-23421 | Linux Kernel up to 6.18.16/6.19.6/7.0-rc2 configfs wa_bb_store allocation of resources

VDB-355100 · CVE-2026-23421 · GCVE-0-2026-23421 LINUX KERNEL UP TO 6.18.16/6.19.6/7.0-RC2 CONFIGFS WA_BB_STORE ALLOCATION OF RESOURCES HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.5 $0-$5k 0.46+ Summaryinfo A vulnerability was found in Linux Kernel up to 6.18.16/6.19.6/7.0-rc2 and classified as critical. This impacts the function wa_bb_store of the component configfs. Such manipulation leads to allocation of resources. This vulnerability is referenced as CVE-2026-23421. No exploit is available. It is suggested to upgrade the affected component. Detailsinfo A vulnerability was found in Linux Kernel up to 6.18.16/6.19.6/7.0-rc2 and classified as critical. Affected by this issue is the function wa_bb_store of the component configfs. The manipulation with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is availability. CVE summarizes: In the Linux kernel, the following vulnerability has been resolved: drm/xe/configfs: Free ctx_restore_mid_bb in release ctx_restore_mid_bb memory is allocated in wa_bb_store(), but xe_config_device_release() only frees ctx_restore_post_bb. Free ctx_restore_mid_bb[0].cs as well to avoid leaking the allocation when the configfs device is removed. (cherry picked from commit a235e7d0098337c3f2d1e8f3610c719a589e115f) The advisory is shared for download at git.kernel.org. This vulnerability is handled as CVE-2026-23421 since 01/13/2026. There are known technical details, but no exploit is available. Upgrading to version 6.18.17, 6.19.7 or 7.0-rc3 eliminates this vulnerability. Applying the patch 7f971dfd48983074adc7bbcea3ee95ce7aad47cb/3557359ea3df32430ea7c30f7a708ca9a91d7e0e/e377182f0266f46f02d01838e6bde67b9dac0d66 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 7.0-rc2 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: 5.7 VulDB Meta Temp Score: 5.5 VulDB Base Score: 5.7 VulDB Temp Score: 5.5 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: Allocation of resources CWE: CWE-770 / CWE-400 / CWE-404 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-rc3 Patch: 7f971dfd48983074adc7bbcea3ee95ce7aad47cb/3557359ea3df32430ea7c30f7a708ca9a91d7e0e/e377182f0266f46f02d01838e6bde67b9dac0d66 Timelineinfo 01/13/2026 CVE reserved 04/03/2026 +79 days Advisory disclosed 04/03/2026 +0 days VulDB entry created 04/03/2026 +0 days VulDB entry last update Sourcesinfo Vendor: kernel.org Advisory: git.kernel.org Status: Confirmed CVE: CVE-2026-23421 (🔒) GCVE (CVE): GCVE-0-2026-23421 GCVE (VulDB): GCVE-100-355100 Entryinfo Created: 04/03/2026 17:04 Changes: 04/03/2026 17:04 (59) Complete: 🔍 Cache ID: 99:775:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸