Security readout for executives and security teams
Plain-English summary
This Linux kernel flaw can cause expected audit records for a syscall to be missing. The main risk is not direct compromise from the source evidence, but weakened accountability, compliance evidence, and incident investigation on systems that depend on Linux audit logs.
Executive priority
Handle as an audit integrity issue. Prioritize regulated, high-value, and investigation-critical Linux systems, but avoid emergency exploitation claims because the provided sources do not support them.
Technical view
CVE-2020-35501 concerns the Linux kernel audit rules implementation. A syscall may unexpectedly not be logged by the audit subsystem. The bundle lists kernel versions up to 5.17 as affected, with CWE-863, but provides no CVSS score, patch details, or exploit prerequisites.
Likely exposure
Exposure is most relevant on Linux systems running affected kernels up to 5.17 that rely on auditd or kernel audit rules for compliance, monitoring, or forensic reconstruction.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. It also does not provide exploit mechanics, required privileges, or reliable attack conditions.
Researcher notes
Evidence is limited to the CVE description, affected kernel range, CWE, and Red Hat Bugzilla reference. No CVSS, patch commit, exploit status, or technical reproducer is included in the provided bundle.
Mitigation direction
- Inventory Linux hosts and kernel versions against vendor advisories for CVE-2020-35501.
- Prioritize systems where Linux audit logs support compliance, privileged activity monitoring, or investigations.
- Apply vendor-supported kernel updates when guidance identifies a fixed package or backport.
- Treat affected audit logs as potentially incomplete until vendor remediation is confirmed.
- Use additional telemetry sources for sensitive activity monitoring during remediation.
Validation and detection
- Confirm whether hosts run Linux kernel versions listed as affected by vendor guidance.
- Check whether auditd or kernel audit rules are enabled and operationally relied upon.
- Review vendor errata for fixed kernel packages or backported patches.
- After remediation, verify expected audit events are recorded for relevant control requirements.
- Review SIEM detections that depend only on Linux audit events.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2020-35501 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://bugzilla.redhat.com/show_bug.cgi?id=1908577CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.