Answer in brief
CVE-2025-39694 records a Unknown severity vulnerability in s390/sclp: Fix SCCB present check. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ada1da31ce34248bc97ca8f801f2cf6efa378a81 <aa5073ac1a2a274812f3b04c278992e68ff67cc7 || >=ada1da31ce34248bc97ca8f801f2cf6efa378a81 <86c2825791c3836a8f77a954b9c5ebe6fab410c5 || >=ada1da31ce34248bc97ca8f801f2cf6efa378a81 <61605c847599fbfdfafe638607841c7d73719081 || >=ada1da31ce34248bc97ca8f801f2cf6efa378a81 <bf83ae3537359af088d6577812ed93113dfbcb7b || >=ada1da31ce34248bc97ca8f801f2cf6efa378a81 <430fa71027b6ac9bb0ce5532b8d0676777d4219a | aa5073ac1a2a274812f3b04c278992e68ff67cc7, 86c2825791c3836a8f77a954b9c5ebe6fab410c5, 61605c847599fbfdfafe638607841c7d73719081, bf83ae3537359af088d6577812ed93113dfbcb7b, 430fa71027b6ac9bb0ce5532b8d0676777d4219a |
| Linux/Linuxgeneric | 5.16 | Not reported |
| Siemens/SIMATIC CN 4100generic | >=0 <V5.0 | V5.0 |
Published upstream
Sep 5, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: s390/sclp: Fix SCCB present check Tracing code called by the SCLP interrupt handler contains early exits if the SCCB address associated with an interrupt is NULL. This check is performed after physical to virtual address translation. If the kernel identity mapping does not start at address zero, the resulting virtual address is never zero, so that the NULL checks won't work. Subsequently this may result in incorrect accesses to the first page of the identity mapping. Fix this by introducing a function that handles the NULL case before address translation.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-39694 records a Unknown severity vulnerability in s390/sclp: Fix SCCB present check. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC CN 4100 (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ada1da31ce34248bc97ca8f801f2cf6efa378a81 <aa5073ac1a2a274812f3b04c278992e68ff67cc7 || >=ada1da31ce34248bc97ca8f801f2cf6efa378a81 <86c2825791c3836a8f77a954b9c5ebe6fab410c5 || >=ada1da31ce34248bc97ca8f801f2cf6efa378a81 <61605c847599fbfdfafe638607841c7d73719081 || >=ada1da31ce34248bc97ca8f801f2cf6efa378a81 <bf83ae3537359af088d6577812ed93113dfbcb7b || >=ada1da31ce34248bc97ca8f801f2cf6efa378a81 <430fa71027b6ac9bb0ce5532b8d0676777d4219a | aa5073ac1a2a274812f3b04c278992e68ff67cc7, 86c2825791c3836a8f77a954b9c5ebe6fab410c5, 61605c847599fbfdfafe638607841c7d73719081, bf83ae3537359af088d6577812ed93113dfbcb7b, 430fa71027b6ac9bb0ce5532b8d0676777d4219a |
| Linux/Linuxgeneric | 5.16 | Not reported |
| Siemens/SIMATIC CN 4100generic | >=0 <V5.0 | V5.0 |
Published upstream
Sep 5, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: s390/sclp: Fix SCCB present check Tracing code called by the SCLP interrupt handler contains early exits if the SCCB address associated with an interrupt is NULL. This check is performed after physical to virtual address translation. If the kernel identity mapping does not start at address zero, the resulting virtual address is never zero, so that the NULL checks won't work. Subsequently this may result in incorrect accesses to the first page of the identity mapping. Fix this by introducing a function that handles the NULL case before address translation.
Quoted source text, attributed separately from HOL analysis.