CVE-2024-35943: pmdomain: ti: Add a null pointer check to the omap_prm_domain_init
In the Linux kernel, the following vulnerability has been resolved:
pmdomain: ti: Add a null pointer check to the omap_prm_domain_init
devm_kasprintf() returns a pointer to dynamically allocated memory
which can be NULL upon failure. Ensure the allocation was successful
by checking the pointer validity.
Security readout for executives and security teams
Plain-English summary
CVE-2024-35943 is a Linux kernel reliability flaw in TI power-domain initialization. A memory allocation can fail, and the code previously did not check for that failure before use. The source bundle does not provide CVSS, impact detail, or evidence of active exploitation.
Executive priority
Treat as a routine kernel maintenance item unless asset review shows exposed critical systems. There is no source-backed evidence of active exploitation or severity scoring, so urgency should follow normal kernel patch governance and vendor guidance.
Technical view
The issue is in pmdomain/ti omap_prm_domain_init. devm_kasprintf() may return NULL on allocation failure, and the fix adds a null pointer validity check. Public references are Linux stable commits and Debian LTS advisories, but the bundle does not describe privilege requirements or exploitability.
Likely exposure
Exposure is limited to Linux kernels that include the affected TI pmdomain OMAP code in the source-listed version ranges. Systems should rely on their distribution kernel advisories, because the bundle does not provide a complete product matrix or CVSS scope.
Exploitation context
The bundle says KEV is false and provides no cited evidence of active exploitation. The described condition is allocation failure leading to unsafe null pointer handling; practical exploitability and business impact are not established in the provided sources.
Researcher notes
Root cause is an unchecked devm_kasprintf() allocation in omap_prm_domain_init. The fix pattern is defensive null checking. The source bundle lacks CVSS, CWE, reachable attack scenario, and exploit status, so avoid claims beyond reliability and kernel hardening.
Mitigation direction
Update affected Linux kernels through the system vendor or distribution channel.
Confirm the relevant Linux stable fix is included in deployed kernel packages.
Review Debian LTS advisories if running Debian long-term support kernels.
Monitor vendor guidance for corrected versions and backport status.
Validation and detection
Inventory deployed kernel versions and compare them with vendor advisory status.
Check whether running kernels include the referenced stable commits or distribution backports.
Prioritize systems using kernels with TI OMAP power-domain support enabled.
Document exceptions where vendor packages are not yet fixed.
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-35943 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.