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.
Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw on IBM Z/s390 systems can make the SCLP interrupt path access the wrong memory page. Successful exploitation requires local, low-privileged access, but the assessed impact includes serious information exposure and system disruption.
Executive priority
Prioritize confirmation and patching for exposed or multi-user s390 environments. Other architectures are not identified as affected by this bundle. Escalate systems processing sensitive data because the assessed confidentiality and availability impacts are high.
Technical view
The SCLP tracing path checks for a missing SCCB after physical-to-virtual translation. When the kernel identity mapping does not begin at zero, that translation cannot produce a NULL address, allowing incorrect access to the identity mapping’s first page. The fix handles NULL before translation.
Likely exposure
Exposure is limited to Linux on the s390 architecture using the affected SCLP code. The bundle identifies several affected kernel versions, but its version data is irregular; confirm exposure using distribution or product advisories and the referenced stable fixes.
Exploitation context
The CVSS 3.1 vector scores this 7.3 and requires local access with low privileges, without user interaction. Potential impacts are high confidentiality and availability loss with limited integrity impact. The bundle marks KEV false and provides no evidence of active exploitation.
Researcher notes
No CWE is assigned in the supplied record. The vulnerable condition depends on a nonzero-start identity mapping and SCCB handling in the SCLP interrupt tracing path. The five stable-tree commits appear to be branch-specific fixes. Public evidence supplied here does not establish exploitability in practice or active attacks.
Mitigation direction
Install a vendor-supported kernel containing the referenced SCCB address-check fix.
Prioritize affected multi-user or sensitive s390 systems where local access is available.
Consult Linux distribution and appliance vendor guidance for exact fixed package versions.
Reboot into the updated kernel when required by vendor procedures.
Validation and detection
Inventory Linux hosts and appliances running on s390 or s390x architecture.
Record each system’s active kernel and vendor package version.
Compare kernel provenance against vendor advisories and the five referenced stable commits.
After remediation, verify the running kernel is the updated version.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-39694 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
2ADP providers
8Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.