CVE-2025-38433 Details
Description
In the Linux kernel, the following vulnerability has been resolved: riscv: fix runtime constant support for nommu kernels the `__runtime_fixup_32` function does not handle the case where `val` is zero correctly (as might occur when patching a nommu kernel and referring to a physical address below the 4GiB boundary whose upper 32 bits are all zero) because nothing in the existing logic prevents the code from taking the `else` branch of both nop-checks and emitting two `nop` instructions. This leaves random garbage in the register that is supposed to receive the upper 32 bits of the pointer instead of zero that when combined with the value for the lower 32 bits yields an invalid pointer and causes a kernel panic when that pointer is eventually accessed. The author clearly considered the fact that if the `lui` is converted into a `nop` that the second instruction needs to be adjusted to become an `li` instead of an `addi`, hence introducing the `addi_insn_mask` variable, but didn't follow that logic through fully to the case where the `else` branch executes. To fix it just adjust the logic to ensure that the second `else` branch is not taken if the first instruction will be patched to a `nop`.
A vulnerability in the Linux kernel's handling of runtime constant support for RISC-V NOMMU kernels has been addressed. The issue arose in the `__runtime_fixup_32` function, which improperly managed cases where the `val` parameter was zero. This mismanagement could occur when patching a NOMMU kernel and referencing a physical address below the 4 GiB threshold, where the upper 32 bits were all zero. The existing logic allowed the function to incorrectly emit two `nop` instructions, leaving random data in the register intended for the upper 32 bits of a pointer. When this corrupted data was combined with the lower 32 bits, it resulted in an invalid pointer, causing a kernel panic upon access. The vulnerability was rooted in the failure to fully apply the logic of adjusting the second instruction to an `li` after converting the first to a `nop`, particularly when the `else` branch of the nop-checks was executed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/0a24b00dcde83934a3cc13e4c6b775522903496b | kernel.org | Patch |
| https://git.kernel.org/stable/c/8d90d9872edae7e78c3a12b98e239bfaa66f3639 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-476 | NULL Pointer Dereference | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.15, < 6.15.5 6.16 rc1 6.16 rc2 6.16 rc3 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 19, 2025 | Initial Analysis | [email protected] |
| Jul 25, 2025 | New CVE Received | kernel.org |