Security readout for executives and security teams
Plain-English summary
A Linux kernel type mismatch in NVIDIA’s ARM SMMU fault handler can calculate an invalid memory address and crash the kernel. The supplied evidence shows a kernel NULL-pointer failure on NVIDIA Jetson Orin NX hardware. This is primarily a local risk; remote exploitation is not supported by the sources.
Executive priority
Treat as a high-priority stability and local-security update for exposed NVIDIA ARM platforms. Accelerate remediation where untrusted users or workloads have local execution. Other Linux systems should first validate driver and hardware applicability before emergency action.
Technical view
The interrupt callback nvidia_smmu_context_fault() received an incorrectly typed pointer. Because iommu_domain is embedded at a non-zero structure offset, the handler derived the wrong address and dereferenced invalid memory near 0x120. Stable-kernel commits correct the callback types.
Likely exposure
Exposure is most likely on ARM Linux systems exercising the NVIDIA SMMU driver path. The bundle names Linux 6.8, 6.8.10, and 6.9, but does not clearly preserve complete version-range semantics. Confirm affected status against kernel or distribution advisories.
Exploitation context
The CVSS 3.1 score is 7.8 with local access and low privileges required. The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation or a public exploit. They demonstrate a kernel crash, not confirmed confidentiality or integrity compromise.
Researcher notes
The documented failure occurred while freeing an IRQ during SMMU domain teardown on Jetson Orin NX, following deferred PCIe probing. Although CVSS assigns high confidentiality, integrity, and availability impacts, the supplied technical evidence directly establishes only an invalid pointer dereference and kernel Oops. No CWE is provided.
Mitigation direction
Upgrade to a vendor-supported kernel containing one of the referenced stable fixes.
Prioritize ARM systems using the NVIDIA SMMU driver and permitting local untrusted workloads.
Check distribution or device-vendor guidance for exact fixed package versions.
If upgrades are delayed, restrict local access and untrusted workload execution where operationally feasible.
Validation and detection
Record the running kernel and distribution package versions on potentially exposed ARM systems.
Confirm whether the NVIDIA ARM SMMU driver and affected handler are present or active.
Verify the deployed kernel includes either referenced stable-kernel correction.
Review kernel logs for nvidia_smmu_context_fault, NULL-pointer dereferences, or address 0x120 crashes.
Recheck package status against current kernel or distribution security advisories.
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-2024-36884 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.
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.