CVE-2024-35947: dyndbg: fix old BUG_ON in >control parser
In the Linux kernel, the following vulnerability has been resolved:
dyndbg: fix old BUG_ON in >control parser
Fix a BUG_ON from 2009. Even if it looks "unreachable" (I didn't
really look), lets make sure by removing it, doing pr_err and return
-EINVAL instead.
Security readout for executives and security teams
Plain-English summary
CVE-2024-35947 is a Linux kernel denial-of-service issue in the dynamic debug control parser. A local low-privileged user could trigger a kernel BUG condition, causing availability impact. The public record shows kernel stable fixes and distro notices, but no KEV listing or cited evidence of active exploitation.
Executive priority
Handle through normal kernel patch management, with higher priority on multi-user systems, shared compute, CI runners, and hosts running untrusted workloads. This is an availability risk, not a confirmed data breach or remote compromise issue.
Technical view
The fix changes an old BUG_ON path in the Linux kernel dyndbg control parser to log an error and return -EINVAL. CVSS 3.1 is 5.5: local attack vector, low complexity, low privileges, no user interaction, and high availability impact only.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel lines and allowing local users or workloads to reach the dynamic debug control path. Internet-facing remote exposure is not supported by the provided CVSS vector or sources.
Exploitation context
The source bundle supports local, low-privilege denial of service potential. It does not support remote exploitation, data theft, privilege escalation, or active exploitation. KEV status is false in the provided record.
Researcher notes
The public description is terse and does not provide a CWE. The important signal is the replacement of BUG_ON with graceful error handling in dyndbg parsing. Research should focus on affected kernel lineage and vendor backports, not on assuming broader impact.
Mitigation direction
Update affected Linux kernels using vendor-supported fixed packages.
Prioritize Debian LTS and Fedora systems referenced by the advisories.
Check kernel stable commits or distribution changelogs for the dyndbg fix.
Reboot systems after kernel updates so the fixed kernel is active.
Where patching is delayed, restrict unnecessary local user access.
Validation and detection
Inventory Linux kernel versions across servers, workstations, and appliances.
Compare installed kernels with vendor advisories and fixed package versions.
Confirm rebooted systems are running the patched kernel, not only installed packages.
Review vulnerability scanner findings for CVE-2024-35947 accuracy.
Check vendor guidance for any platform-specific remediation notes.
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-35947 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.