LiveActive security incident?Get immediate response
CVE Record

CVE-2020-28588: An information disclosure vulnerability exists in the /proc/pid/syscall functionality of Linux Kernel 5.1 S...

An information disclosure vulnerability exists in the /proc/pid/syscall functionality of Linux Kernel 5.1 Stable and 5.4.66. More specifically, this issue has been introduced in v5.1-rc4 (commit 631b7abacd02b88f4b0795c08b54ad4fc3e7c7c0) and is still present in v5.10-rc4, so it’s likely that all versions in between are affected. An attacker can read /proc/pid/syscall to trigger this vulnerability, which leads to the kernel leaking memory contents.

MediumCVSS 4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can let a local attacker read memory contents through the /proc pid syscall interface. It is not a remote takeover issue, but it matters on shared Linux systems, build hosts, developer workstations, and container platforms where untrusted users can run code.

Executive priority

Treat this as a moderate-priority Linux fleet hygiene issue. It is not described as remotely exploitable, but it can expose sensitive memory on affected shared systems and should be folded into kernel patching and hardening work.

Technical view

CVE-2020-28588 is an information disclosure flaw in Linux Kernel /proc/pid/syscall functionality. Sources say it was introduced in v5.1-rc4 and remained present through v5.10-rc4, likely affecting versions between. Reading /proc/pid/syscall can trigger leakage of kernel memory contents. CVSS is 4.0, local, low complexity, no privileges, confidentiality impact only.

Likely exposure

Exposure is most relevant where affected Linux kernel versions are used and untrusted local users, workloads, or containers can access procfs. Single-purpose systems with no local untrusted execution have lower practical risk.

Exploitation context

The provided sources do not show active exploitation, and the CVE is not marked KEV. Exploitation requires local access, but the CVSS vector indicates no privileges and no user interaction are required once local execution is available.

Researcher notes

Evidence is limited to public CVE metadata and Talos reporting referenced in the bundle. The source describes affected upstream versions and the vulnerable procfs functionality, but the bundle does not name a specific fixed version, workaround, or observed exploitation.

Mitigation direction

  • Inventory Linux systems running kernels from v5.1-rc4 through v5.10-rc4.
  • Check Linux distribution or kernel vendor guidance for fixed packages or backports.
  • Prioritize shared hosts, CI runners, developer machines, and container infrastructure.
  • Limit untrusted local shell, workload, or container access on affected systems.
  • Apply vendor-supported kernel updates after testing.

Validation and detection

  • Confirm kernel versions against the affected range in the CVE sources.
  • Review distribution advisories for whether fixes were backported to installed packages.
  • Identify systems where untrusted users or workloads can access procfs.
  • Confirm whether /proc pid syscall exposure matches local hardening policy.
  • Document compensating controls where patching cannot happen immediately.
Prepared
Confidence
medium
Sources
3

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.

cwe · low confidence lookup

CWE-681: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
cve · low confidence lookup

CVE-2020-28588 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
4CVSS 3.0MediumCVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N2.51.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

4Medium
CVSS 3.0 vector shape for CVE-2020-28588Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aLinux KernelLinux Kernel v5.10-rc4,Linux Kernel v5.4.66,Linux Kernel v5.9.8Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-681 · source CWE mapping

Incorrect Conversion between Numeric Types

Incorrect Conversion between Numeric Types represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.