CVE-2026-23995
Stack-Based Buffer Overflow in EVerest CAN Interface Enables Code Execution
Publication date: 2026-03-26
Last updated on: 2026-03-31
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linuxfoundation | everest | to 2026.02.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-121 | A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows local attackers to execute arbitrary code with high impact on confidentiality, integrity, and availability. Such a compromise could lead to unauthorized access or manipulation of sensitive data, which may affect compliance with standards like GDPR and HIPAA that require protection of personal and health information.
However, the provided information does not explicitly discuss compliance implications or specific regulatory impacts.
Can you explain this vulnerability to me?
CVE-2026-23995 is a high-severity stack-based buffer overflow vulnerability in the EVerest EV charging software stack's CAN interface initialization code.
The vulnerability occurs when an interface name longer than 16 bytes (the size of the ifreq.ifr_name buffer) is passed to CAN open routines. Because the code uses an unsafe string copy function without length checks, this causes the buffer to overflow, corrupting adjacent stack data.
This overflow happens before any privilege checks or interface existence verification, meaning a malicious or misconfigured interface name can trigger it even without privileges or user interaction.
Exploitation can lead to arbitrary code execution by causing stack corruption.
How can this vulnerability impact me? :
This vulnerability allows an attacker with local access and no privileges to execute arbitrary code on the affected system.
Successful exploitation can compromise confidentiality, integrity, and availability of the system, as indicated by the high impact scores.
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
Because the vulnerability can be triggered without privileges or user interaction, it poses a significant risk to system security.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability arises when an interface name longer than 16 bytes (IFNAMSIZ) is passed to CAN open routines, causing a stack-based buffer overflow. Detection involves checking for network interfaces or configurations with interface names exceeding this length.
You can list network interfaces and check their names using commands like:
- ip link show
- ifconfig -a
Look for any interface names longer than 15 characters (since the buffer size is 16 including the null terminator). Any such interface name could potentially trigger the vulnerability.
Additionally, reviewing configuration files or environment variables that set interface names for the EVerest CAN interface initialization routines may help identify malicious or misconfigured names.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation is to upgrade the EVerest software stack to version 2026.02.0 or later, where the vulnerability has been patched.
Until the upgrade can be applied, ensure that no interface names longer than 16 bytes are used or allowed in the system, especially for CAN interfaces.
Restrict local user access to prevent attackers from creating or influencing interface names, as the vulnerability requires local access but no privileges.
Monitor system logs and behavior for any signs of exploitation attempts involving CAN interface initialization.