Security readout for executives and security teams
Plain-English summary
This Linux kernel issue could let a local unprivileged user running BPF read sensitive kernel memory through a CPU side channel. That makes it mainly a confidentiality risk on shared Linux systems, build hosts, containers, and multi-user servers.
Executive priority
Treat this as a timely kernel patching issue for shared Linux infrastructure. Urgency is lower than remote code execution, but confidentiality impact can matter where untrusted local users or workloads coexist.
Technical view
Linux kernels through 5.13.7 are described as vulnerable when unprivileged BPF programs interact with Speculative Store Bypass behavior. The issue involves store ordering where an attacker-controlled value may affect a side-channel path before a protective store occurs.
Likely exposure
Exposure is most likely on Linux systems running kernels through 5.13.7 or older vendor kernels without the relevant backports, especially where unprivileged BPF is available to local users or workloads.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. The described attack is local and side-channel based; it requires the ability to run an unprivileged BPF program, not just remote network access.
Researcher notes
Evidence is strongest for upstream Linux and listed distro advisories. The bundle lacks CVSS, CWE, and detailed affected CPEs, so validate against vendor backport status rather than upstream version alone.
Mitigation direction
- Update Linux kernel packages using applicable vendor security advisories.
- Confirm distro kernels include the referenced upstream fixes or backports.
- Review whether unprivileged BPF can be restricted until patched.
- Follow Linux vendor guidance for your exact kernel branch.
Validation and detection
- Inventory Linux kernel versions across servers, containers, and build hosts.
- Check whether affected systems allow unprivileged BPF use.
- Verify Fedora, Debian, or vendor advisory fixes are installed.
- Prioritize shared or multi-tenant Linux systems for confirmation.
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.
CVE-2021-35477 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://www.openwall.com/lists/oss-security/2021/08/01/3CVE reference · x_refsource_MISC
- https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/patch/?id=f5e81d1117501546b7be050c5fbafa6efd2c722cCVE reference · x_refsource_MISC
- https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/patch/?id=2039f26f3aca5b0e419b98f65dd36481337b86eeCVE reference · x_refsource_MISC
- FEDORA-2021-4d4d3866caCVE reference · vendor-advisory, x_refsource_FEDORA
- FEDORA-2021-54ee631709CVE reference · vendor-advisory, x_refsource_FEDORA
- [debian-lts-announce] 20211015 [SECURITY] [DLA 2785-1] linux-4.19 security updateCVE reference · mailing-list, x_refsource_MLIST
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.
