Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects IBM s390 systems. A low-memory kernel area could remain mapped at address zero, so some NULL pointer accesses may succeed instead of faulting. The public bundle does not state a complete impact, severity score, or active exploitation.
Executive priority
Treat this as architecture-specific kernel risk. Prioritize validation for business-critical IBM Z or s390 Linux systems, but do not escalate as active exploitation without new evidence.
Technical view
On s390, the identity mapping pinned at address zero also maps lowcore. With relocate_lowcore, lowcore can be mapped twice. The fix avoids identity mapping the first two physical memory pages, restoring expected NULL access exceptions where low address protection is incomplete.
Likely exposure
Exposure appears limited to Linux deployments on s390 architecture running affected kernel versions or commits identified in the CVE data. Non-s390 systems are not indicated as affected in the provided sources.
Exploitation context
No active exploitation is stated. The CVE is not marked KEV, and the bundle provides no exploit reports, proof-of-concept references, or attacker prerequisites.
Researcher notes
The source bundle lacks CVSS, CWE, detailed impact, and exploitability analysis. Research should focus on affected s390 kernel ranges, vendor backports, and whether NULL access behavior creates reachable privilege or availability impact.
Mitigation direction
- Update to a Linux kernel containing the referenced stable fixes.
- Confirm distributor advisories for your exact s390 kernel package.
- Prioritize s390 hosts running kernels listed as affected in the CVE data.
- Avoid relying on assumed mitigations not confirmed by vendor guidance.
Validation and detection
- Inventory Linux hosts by architecture and kernel version.
- Identify s390 systems using affected upstream or vendor kernel builds.
- Verify whether the referenced stable commits are present in deployed kernels.
- Check vendor security advisories for package-specific fixed versions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2025-38733 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
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.
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/30bf5728bb217a6d1ba73f44094c9b9c6bc9a567CVE reference, Linux
- https://git.kernel.org/stable/c/1d7864acd497cb468a998d44631f84896f885e85CVE reference, Linux
- https://git.kernel.org/stable/c/93f616ff870a1fb7e84d472cad0af651b18f9f87CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.