CVE-2026-31395 | Linux Kernel up to 6.18.19/6.19.9/7.0-rc4 bnxt_en bnxt_async_event_process memory corruption
VulDBArchived Apr 03, 2026✓ Full text saved
A vulnerability classified as critical has been found in Linux Kernel up to 6.18.19/6.19.9/7.0-rc4 . This affects the function bnxt_async_event_process of the component bnxt_en . This manipulation causes memory corruption. This vulnerability is registered as CVE-2026-31395 . The attack requires access to the local network. No exploit is available. It is recommended to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-355166 · CVE-2026-31395 · GCVE-0-2026-31395
LINUX KERNEL UP TO 6.18.19/6.19.9/7.0-RC4 BNXT_EN BNXT_ASYNC_EVENT_PROCESS MEMORY CORRUPTION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
7.6 $5k-$25k 0.84
Summaryinfo
A vulnerability classified as critical was found in Linux Kernel up to 6.18.19/6.19.9/7.0-rc4. This impacts the function bnxt_async_event_process of the component bnxt_en. Such manipulation leads to memory corruption. This vulnerability is documented as CVE-2026-31395. There is not any exploit available. Upgrading the affected component is advised.
Detailsinfo
A vulnerability was found in Linux Kernel up to 6.18.19/6.19.9/7.0-rc4. It has been rated as critical. Affected by this issue is the function bnxt_async_event_process of the component bnxt_en. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. CVE summarizes:
In the Linux kernel, the following vulnerability has been resolved: bnxt_en: fix OOB access in DBG_BUF_PRODUCER async event handler The ASYNC_EVENT_CMPL_EVENT_ID_DBG_BUF_PRODUCER handler in bnxt_async_event_process() uses a firmware-supplied 'type' field directly as an index into bp->bs_trace[] without bounds validation. The 'type' field is a 16-bit value extracted from DMA-mapped completion ring memory that the NIC writes directly to host RAM. A malicious or compromised NIC can supply any value from 0 to 65535, causing an out-of-bounds access into kernel heap memory. The bnxt_bs_trace_check_wrap() call then dereferences bs_trace->magic_byte and writes to bs_trace->last_offset and bs_trace->wrapped, leading to kernel memory corruption or a crash. Fix by adding a bounds check and defining BNXT_TRACE_MAX as DBG_LOG_BUFFER_FLUSH_REQ_TYPE_ERR_QPC_TRACE + 1 to cover all currently defined firmware trace types (0x0 through 0xc).
The advisory is available at git.kernel.org. This vulnerability is handled as CVE-2026-31395 since 03/09/2026. The exploitation is known 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 04/03/2026).
Upgrading to version 6.18.20, 6.19.10 or 7.0-rc5 eliminates this vulnerability. Applying the patch 19aa416eed9e4aaf1bbe8da0f7bd9a9be31158c8/b7c7a275447c6d4bf4a36a134682e2e4e20efd4b/64dcbde7f8f870a4f2d9daf24ffb06f9748b5dd3 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.18.17
6.18.18
6.18.19
6.19.0
6.19.1
6.19.2
6.19.3
6.19.4
6.19.5
6.19.6
6.19.7
6.19.8
6.19.9
7.0-rc1
7.0-rc2
7.0-rc3
7.0-rc4
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.20/6.19.10/7.0-rc5
Patch: 19aa416eed9e4aaf1bbe8da0f7bd9a9be31158c8/b7c7a275447c6d4bf4a36a134682e2e4e20efd4b/64dcbde7f8f870a4f2d9daf24ffb06f9748b5dd3
Timelineinfo
03/09/2026 CVE reserved
04/03/2026 +24 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-31395 (🔒)
GCVE (CVE): GCVE-0-2026-31395
GCVE (VulDB): GCVE-100-355166
Entryinfo
Created: 04/03/2026 18:17
Changes: 04/03/2026 18:17 (60)
Complete: 🔍
Cache ID: 99:768:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸