CVE-2026-97507
Description
A flaw was found in the Linux kernel's DM1105 media driver. A local user could cause a Denial of Service (DoS) through a kernel crash if Direct Memory Access (DMA) memory allocation fails during device initialization. Because the driver ignores the allocation return value, it proceeds to use a null pointer for subsequent DMA transfers, resulting in invalid memory access and system failure.
Statement
A moderate severity flaw was found in the Linux kernel DM1105 media (DVB) driver. In dm1105_hw_init(), the return value of dm1105_dma_map(), which performs the DMA memory allocation via dma_alloc_coherent(), is not checked. If that allocation fails, for example under memory pressure, driver initialization continues and the driver proceeds to use a NULL pointer for subsequent DMA transfers, leading to invalid memory access and a kernel oops. A local user able to trigger device initialization when the DMA allocation fails can therefore cause a denial of service (system crash). Confidentiality and integrity are not impacted (Red Hat CVSS 5.5, CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
Within Red Hat's product portfolio, Red Hat Enterprise Linux 7 and 8 (kernel and kernel-rt) and the RHEL CoreOS 8 based OpenShift Container Platform 4.12 are affected; fixes for these streams are currently deferred because the flaw is a local denial of service that requires uncommon conditions (the presence of DM1105 hardware and a failed DMA allocation during driver initialization), and the residual risk is limited to a local kernel crash on such systems. Red Hat Enterprise Linux 9 and 10, Red Hat In-Vehicle OS, and the RHEL CoreOS 9 based OpenShift versions are not affected because the vulnerable code is not present in those releases.
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.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart
NULL pointer dereferences usually result in the failure of the process unless exception handling (on some platforms) is available and implemented. Even when exception handling is being used, it can still be very difficult to return the software to a safe state of operation.
Integrity,Confidentiality
Technical Impact: Execute Unauthorized Code or Commands; Read Memory; Modify Memory
In rare circumstances, when NULL is equivalent to the 0x0 memory address and privileged code can access it, then writing or reading memory is possible, which may lead to code execution.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
