Security readout for executives and security teams
Plain-English summary
This is a Linux kernel information leak in the traffic-control skbmod action. A kernel structure contained four uninitialized bytes, and the dump path could return those bytes to user space. The sources do not provide CVSS, active exploitation, or a complete exploitability assessment.
Executive priority
Treat as a routine but real kernel confidentiality fix. It does not currently show public active exploitation in the supplied sources, but kernel information leaks can support broader attack chains, especially on shared infrastructure.
Technical view
The vulnerable path is net/sched act_skbmod. tcf_skbmod_dump() copied struct tc_skbmod to netlink output without clearing a four-byte padding hole, allowing kernel stack data disclosure. The fix clears the structure before fields are populated.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions or vendor kernels missing the stable backport. The implicated path is rtnetlink traffic-control action handling. Access prerequisites are not fully stated in the provided sources.
Exploitation context
There is no KEV listing and no cited source states active exploitation. The issue was reported by syzbot using KMSAN. The documented impact is a small kernel stack information leak to user space.
Researcher notes
Key evidence is the syzbot/KMSAN trace showing copy_to_user of uninitialized data through tcf_skbmod_dump(). The affected-version data is incomplete without vendor package mapping, so validation should rely on distribution advisories and commit backports.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Check Debian, Siemens, and other vendor advisories for backported package versions.
Prioritize shared, multi-user, container, and network appliance Linux hosts.
If patch status is unclear, request vendor confirmation for CVE-2024-35893 coverage.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and container hosts.
Compare installed kernels against vendor advisories and stable fix references.
Confirm whether vendor backports include the act_skbmod structure-clearing fix.
Track unresolved systems as confidentiality-risk exceptions until patched or vendor-cleared.
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-35893 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.