Linux Kernel up to 7.1.7 j1939 j1939_session_fresh_new initialization

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 7.1.7. It has been declared as problematic. This affects the function j1939_session_fresh_new of the component j1939. Executing a manipulation can lead to initialization.
This vulnerability is registered as CVE-2026-80707. It is possible to launch the attack remotely. No exploit is available.
It is recommended to upgrade the affected component.
Details
A vulnerability classified as problematic was found in Linux Kernel up to 7.1.7. This vulnerability affects the function j1939_session_fresh_new of the component j1939. The manipulation with an unknown input leads to a initialization vulnerability. The CWE definition for the vulnerability is CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. As an impact it is known to affect confidentiality. CVE summarizes:
In the Linux kernel, the following vulnerability has been resolved: can: j1939: transport: j1939_session_fresh_new(): initialize receive buffer Zero the allocated buffer in j1939_session_fresh_new() to ensure it contains no residual data. While there is a potential performance impact if users allocate maximum sized ETP buffers, most real-world use cases are not noticeably affected since the maximum known buffer size is typically around 65K. [mkl: add Message-ID]
The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2026-80707 since 08/26/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 08/30/2026).
Upgrading to version 5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, 6.18.44 or 7.1.8 eliminates this vulnerability. Applying the patch 348818277a3646d5b9fa60c9d20c00dc4bc86832/f3e120a34b336079479fa10f706f0636eaa6e751/bbfa49d1e287de44994955b44d19281be3195b44/194d67e92197eb820f4c2c6605d9721333b3eba0/038bad8e16c2e28acf31f0b527a816fb23a57269/8604a3b81b9d0ceaf04fee5f52e701f623a179f9/d5b3613c7d69d8dcb4dd6704f1f463198ce9f6cf/eb96c58907922546e415e545fe9a14ea63b02719 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at EUVD (EUVD-2026-67442) and CERT Bund (WID-SEC-2026-3075). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Affected
- Open Source Linux Kernel
Product
Type
Vendor
Name
Version
- 5.10.264
- 5.15.215
- 6.1.182
- 6.6.150
- 6.12.102
- 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.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 7.1.0
- 7.1.1
- 7.1.2
- 7.1.3
- 7.1.4
- 7.1.5
- 7.1.6
- 7.1.7
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 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: 🔍
Exploiting
Class: InitializationCWE: CWE-665
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.10.265/5.15.216/6.1.183/6.6.151/6.12.103/6.18.44/7.1.8
Patch: 348818277a3646d5b9fa60c9d20c00dc4bc86832/f3e120a34b336079479fa10f706f0636eaa6e751/bbfa49d1e287de44994955b44d19281be3195b44/194d67e92197eb820f4c2c6605d9721333b3eba0/038bad8e16c2e28acf31f0b527a816fb23a57269/8604a3b81b9d0ceaf04fee5f52e701f623a179f9/d5b3613c7d69d8dcb4dd6704f1f463198ce9f6cf/eb96c58907922546e415e545fe9a14ea63b02719
Timeline
08/26/2026 CVE reserved08/28/2026 Advisory disclosed
08/28/2026 VulDB entry created
08/30/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-80707 (🔒)
GCVE (CVE): GCVE-0-2026-80707
GCVE (VulDB): GCVE-100-396640
EUVD: 🔒
CERT Bund: WID-SEC-2026-3075 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 08/28/2026 11:00Updated: 08/30/2026 05:52
Changes: 08/28/2026 11:00 (59), 08/29/2026 12:53 (1), 08/30/2026 05:52 (7)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.