CVE-2025-68135
BaseFortify
Publication date: 2026-01-21
Last updated on: 2026-02-06
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linuxfoundation | everest | to 2025.10.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-703 | The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs because the TbdController loop in the EVerest project's ISO15118 charger implementation does not properly handle C++ exceptions. When certain functions within this loop throw exceptions, they are not caught, causing the loop and its caller to silently terminate. This makes the module responsible for SDP and ISO15118-20 servers unusable, leading to a denial of service. The issue can be triggered by sending malformed SDP requests or disconnecting prematurely, which causes exceptions that crash the server loop. [1]
How can this vulnerability impact me? :
The vulnerability can cause a denial of service (DoS) by making the SDP and ISO15118-20 servers unresponsive. An attacker can exploit this by sending malformed SDP requests or invalid data, causing the server loop to crash silently without recovery. This results in the module becoming unusable, disrupting services that rely on these servers. No user interaction or privileges are required to exploit this, and it can be triggered by an adjacent attacker. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the behavior of the ISO15118 charger server, specifically looking for silent termination or unresponsiveness of the TbdController loop. One way to detect it is by sending crafted malformed SDP requests or invalid V2GTP headers via multicast UDP to the server and observing if the server loop crashes or stops responding. For example, using tools like 'netcat' or 'socat' to send malformed packets to the server's listening port could help detect the issue. Additionally, monitoring logs for unexpected termination of the iso15118::read_single_sdp_packet() function or the TbdController loop may indicate the vulnerability being triggered. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade the EVerest software to version 2025.10.0 or later, where the issue with exception handling in the TbdController loop has been fixed. Until the upgrade can be applied, restricting access to the ISO15118 charger server from untrusted or adjacent networks to prevent malicious malformed SDP requests can reduce the risk of exploitation. [1]