CVE-2024-35916: dma-buf: Fix NULL pointer dereference in sanitycheck()
In the Linux kernel, the following vulnerability has been resolved:
dma-buf: Fix NULL pointer dereference in sanitycheck()
If due to a memory allocation failure mock_chain() returns NULL, it is
passed to dma_fence_enable_sw_signaling() resulting in NULL pointer
dereference there.
Call dma_fence_enable_sw_signaling() only if mock_chain() succeeds.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash affected systems if a memory allocation failure leads kernel code to use a missing object. The business impact is availability, not data theft or data modification. The source bundle rates it medium, with CVSS 5.3, and provides upstream stable kernel fixes.
Executive priority
Schedule remediation through standard kernel patch cycles, with higher urgency for systems where downtime has business impact. This is not presented as a data breach issue, but unpatched systems may face avoidable service interruption risk.
Technical view
In dma-buf, sanitycheck() could pass a NULL return from mock_chain() into dma_fence_enable_sw_signaling(), causing a NULL pointer dereference. The fix gates that call on mock_chain() success. The CVSS vector indicates low availability impact and no confidentiality or integrity impact.
Likely exposure
Exposure is limited to Linux systems running affected kernel versions or downstream builds without the referenced stable fixes. Exact exposure depends on kernel branch and vendor backports; validate against vendor package advisories and kernel changelogs.
Exploitation context
The bundle does not show CISA KEV listing or any cited evidence of active exploitation. It describes a NULL dereference triggered by allocation failure, so treat this mainly as a denial-of-service risk unless vendor guidance states otherwise.
Researcher notes
The source evidence is narrow: a Linux kernel dma-buf NULL dereference fixed by checking mock_chain() before enabling software signaling. No CWE is listed. Avoid claiming exploitability beyond the CVSS vector and the availability impact described by the CVE record.
Mitigation direction
Upgrade to a kernel containing the referenced stable fixes.
Check distribution advisories for backported fixes before assuming version numbers are sufficient.
Prioritize internet-facing or high-availability Linux systems first.
Track remediation through normal kernel patch management and reboot workflows.
Validation and detection
Inventory Linux kernel versions across servers, appliances, containers hosts, and images.
Compare running kernels with vendor advisories and the referenced stable commits.
Confirm patched kernels are actually booted after update and reboot.
Review monitoring for kernel crash or availability events on exposed systems.
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-35916 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.