Home/CVE/A memory disclosure flaw was found in the Linux kernel's versions before 4.18.0-193.el8 in the sysctl subsystem when rea
CVE
↯ PDF report

CVE-2020-10774

A memory disclosure flaw was found in the Linux kernel's versions before 4.18.0-193.el8 in the sysctl subsystem when rea

A memory disclosure flaw was found in the Linux kernel's versions before 4.18.0-193.el8 in the sysctl subsystem when reading the /proc/sys/kernel/rh_features file. This flaw allows a local user to read uninitialized values from the kernel memory. The highest threat from this vulnerability is to confidentiality.

MEDIUM · CVSS 5.5 EPSS 0.00262
EPSS exploitation odds0.26% · top 82%
Monitor
  • No active-exploitation, high-EPSS, or public-exploit signals - routine patching cadence
No Sigma yet — build one → YARA rules0
Look this up elsewhere - one-click external pivots
NVDCVE.orgCISAExploit-DBGitHub PoCVulnCheck KEVGreyNoise
▸ How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2020-10774, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
▣

Severity & exploitation scoring

View on NVD →
CVSS base score
5.5
MEDIUMCVSS v3.1 · [email protected]
EPSS exploitation probability
0.26%
Top 82%odds of exploitation in the next 30 days
CVSS metric silhouette
VectorComplexityPrivilegesInteractionScopeConfidentialityIntegrityAvailability
shape grows toward worst-case
SSVC triage
No SSVC vulnrichment for this CVE. CISA's Vulnrichment program scores newer CVEs (~2024 onwards) plus selected older critical ones. Use the EPSS probability + KEV status to triage instead.
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network Adjacent Local Physical
Attack Complexity
Low High
Privileges Required
None Low High
User Interaction
None Required
Scope
Unchanged Changed
Impact - what breaks
Confidentiality
None Low High
Integrity
None Low High
Availability
None Low High
VECTORCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Lifecycle
  1. 27 May 2021Published to NVD
  2. 17 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain
→
◆

ATT&CK techniques

1

Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.

T1068 · Exploitation for Privilege Escalation
▤ Build a SIEM detection for these techniques
▤

CAPEC attack patterns

2

Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.

CAPEC-CAPEC-100 · Overflow Buffers CAPEC-CAPEC-256 · SOAP Array Overflow
⬡

Weakness Classification

CWE-805Buffer Access with Incorrect Length Value
▤

Affected Products & Versions

1
linux kernel< 4.18.0-193.el8
▤

Related CVEs

8
CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row. Not a guess.
CVE-2019-19339 It was found that the Red Hat Enterprise Linux 8 kpatch update did not include t... same CWE-805 MEDIUM CVE-2020-16101 It is possible for an unauthenticated remote DCOM websocket connection to crash ... same CWE-805 HIGH CVE-2020-14509 Multiple memory corruption vulnerabilities exist in CodeMeter (All versions prio... same CWE-805 CRITICAL CVE-2021-3581 Buffer Access with Incorrect Length Value in zephyr. Zephyr versions >= >=2.5.0 ... same CWE-805 HIGH CVE-1999-1442 Bug in AMD K6 processor on Linux 2.0.x and 2.1.x kernels allows local users to c... 1 same product CVE-1999-1285 Linux 2.1.132 and earlier allows local users to cause a denial of service (resou... same product CVE-1999-0656 The ugidd RPC interface, by design, allows remote attackers to enumerate valid u... same product CVE-1999-0431 Linux 2.2.3 and earlier allow a remote attacker to perform an IP fragmentation a... 1 same product
📦

Fixed versions by distribution

72
The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
oracle allbpftool fixed in 0:4.18.0-240.el8
oracle allkernel fixed in 0:4.18.0-240.el8
oracle allkernel-abi-whitelists open
oracle allkernel-core open
oracle allkernel-cross-headers fixed in 0:4.18.0-240.el8
oracle allkernel-debug open
oracle allkernel-debug-core fixed in 0:4.18.0-240.el8
oracle allkernel-debug-devel fixed in 0:4.18.0-240.el8
oracle allkernel-debug-modules fixed in 0:4.18.0-240.el8
oracle allkernel-debug-modules-extra fixed in 0:4.18.0-240.el8
oracle allkernel-devel fixed in 0:4.18.0-240.el8
oracle allkernel-headers fixed in 0:4.18.0-240.el8
oracle allkernel-modules open
oracle allkernel-modules-extra open
oracle allkernel-tools fixed in 0:4.18.0-240.el8
oracle allkernel-tools-libs fixed in 0:4.18.0-240.el8
oracle allkernel-tools-libs-devel fixed in 0:4.18.0-240.el8
oracle allperf open
oracle allpython3-perf fixed in 0:4.18.0-240.el8
rhel 8bpftool open
rhel 8kernel open
rhel 8kernel-abi-whitelists open
rhel 8kernel-core open
rhel 8kernel-debug fixed in 0:4.18.0-240.el8
rhel 8kernel-debug-core fixed in 0:4.18.0-240.el8
rhel 8kernel-debug-devel fixed in 0:4.18.0-240.el8
rhel 8kernel-debug-modules open
rhel 8kernel-debug-modules-extra open
rhel 8kernel-devel fixed in 0:4.18.0-240.el8
rhel 8kernel-modules fixed in 0:4.18.0-240.el8
rhel 8kernel-modules-extra open
rhel 8kernel-rt open
rhel 8kernel-rt-core fixed in 0:4.18.0-240.rt7.54.el8
rhel 8kernel-rt-debug open
rhel 8kernel-rt-debug-core open
rhel 8kernel-rt-debug-devel open
rhel 8kernel-rt-debug-kvm open
rhel 8kernel-rt-debug-modules fixed in 0:4.18.0-240.rt7.54.el8
rhel 8kernel-rt-debug-modules-extra fixed in 0:4.18.0-240.rt7.54.el8
rhel 8kernel-rt-devel fixed in 0:4.18.0-240.rt7.54.el8
rhel 8kernel-rt-kvm open
rhel 8kernel-rt-modules open
rhel 8kernel-rt-modules-extra fixed in 0:4.18.0-240.rt7.54.el8
rhel 8kernel-tools open
rhel 8kernel-tools-libs open
rhel 8kernel-tools-libs-devel open
rhel 8kernel-zfcpdump fixed in 0:4.18.0-240.el8
rhel 8kernel-zfcpdump-core fixed in 0:4.18.0-240.el8
rhel 8kernel-zfcpdump-devel open
rhel 8kernel-zfcpdump-modules open
rhel 8kernel-zfcpdump-modules-extra fixed in 0:4.18.0-240.el8
rhel 8perf fixed in 0:4.18.0-240.el8
rhel 8python3-perf fixed in 0:4.18.0-240.el8
suse sle15cluster-md-kmp-default open
suse sle15dlm-kmp-default open
suse sle15gfs2-kmp-default open
suse sle15kernel-default open
suse sle15kernel-default-base open
suse sle15kernel-default-devel open
suse sle15kernel-default-extra open
suse sle15kernel-default-livepatch open
suse sle15kernel-default-livepatch-devel open
suse sle15kernel-default-man open
suse sle15kernel-devel open
suse sle15kernel-devel-azure open
suse sle15kernel-devel-rt open
suse sle15kernel-macros open
suse sle15kernel-source open
suse sle15kernel-source-azure open
suse sle15kernel-source-rt open
suse sle15ocfs2-kmp-default open
suse sle15reiserfs-kmp-default open
⚑

Vendor Advisories

2
rhsaRHSA-2020:4431Low
rhsaRHSA-2020:4609Important
🔗

References & Sources

1
Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.
https://bugzilla.redhat.com/show_bug.cgi?id=1846964
Issue TrackingThird Party Advisory
◈SOC and Response
◆Detection Engineering
◎Threat Hunting
▲Red Team and Pentest
■Compliance and GRC
◯About
threatengine.sh