cve.bz

CVE-2025-38733 linux linux kernel: NULL Pointer Dereference

5.5 mediumEPSS 0.2%Fix available

Medium (5.5) in linux linux kernel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: s390/mm: Do not map lowcore with identity mapping Since the identity mapping is pinned to address zero the lowcore is always also mapped to address zero, this happens regardless of the relocate_lowcore command line option. If the option is specified the lowcore is mapped twice, instead of only once. This means that NULL pointer accesses will succeed instead of causing an exception (low address protection still applies, but covers only parts). To fix this never map the first two pages of physical memory with the identity mapping.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-476 NULL Pointer Dereference
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-38733 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-38733?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-38733?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-38733 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linuxfrom 6.10.11 before 6.11
Linux6.11 and later

Fixed in

ProductRelease lineFixed in
Linux6.126.12.44
Linux6.166.16.4
Linuxlater releases6.17

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13linux6.12.48-1DEBIAN-CVE-2025-38733 DSA-6008-1
Debian14linux6.16.5-1DEBIAN-CVE-2025-38733
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-38733
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-38733
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-38733
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2025-38733
Ubuntu24.04:LTSlinux-intel, linux-riscv, linux-oem-6.8 and 17 moreno fix listedUBUNTU-CVE-2025-38733
Ubuntu25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-38733
UbuntuPro:Realtime:24.04:LTSlinux-realtime-6.14no fix listedUBUNTU-CVE-2025-38733
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.6.1SUSE-SU-2025:21179-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-64kb, kernel-docs, kernel-syms and 5 more6.12.0-160000.6.1SUSE-SU-2025:21139-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-default-base6.12.0-160000.6.1.160000.2.4SUSE-SU-2025:21139-1
SUSELinux Micro 6.2kernel-default-base6.12.0-160000.6.1.160000.2.4SUSE-SU-2025:21074-1
SUSELinux Micro 6.2kernel-rt, kernel-64kb, kernel-source and 1 more6.12.0-160000.6.1SUSE-SU-2025:21074-1
SUSELinux Micro Extras 6.2kernel-syms, kernel-obs-build6.12.0-160000.6.1SUSE-SU-2026:20560-1
openSUSELeap 16.0kernel-default-base6.12.0-160000.6.1.160000.2.4openSUSE-SU-2025:20081-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 8 more6.12.0-160000.6.1openSUSE-SU-2025:20081-1
Alpaquita25linux-lts6.12.44-r0BELL-CVE-2025-38733
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-38733

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

A low impact flaw was found in the Linux kernel on the s390 architecture. Because the kernel's identity mapping is pinned to address zero, the lowcore, a critical s390 memory region, was always also mapped at address zero regardless of the relocate_lowcore kernel command-line option; when that option is specified the lowcore is even mapped twice. As a result, NULL pointer accesses could succeed instead of causing an exception, since low-address protection still applies but only covers parts of the lowcore. A local attacker able to trigger such an access could use this flaw to cause a denial of service by crashing the system. The vulnerable code is present in the kernel and kernel-rt packages of Red Hat Enterprise Linux 9 and Red Hat Enterprise Linux 10 and in the kernel package of Red Hat In-Vehicle OS 1. For these affected products the fix is deferred to a future update, as the flaw is assessed as low impact, requires local access, and is limited to the s390 architecture; the residual risk is that a local user on an affected s390 system could trigger a system crash until a fix is delivered. Red Hat Enterprise Linux 6, 7, and 8 are not affected because the vulnerable code is not present in those releases. Red Hat rates this flaw Low severity (CVSS 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H); this is lower than the CVE.org score of 7.8 (Important) because Red Hat's assessment reflects availability-only impact on s390 systems, while the CVE.org vector also claims high confidentiality and integrity impact.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-38733.

References

Check your stackJSON