Linux Kernel up to 5.8-rc5 ZRAM Kernel hot_add Kernel Memory resource consumption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Linux Kernel up to 5.8-rc5. Affected by this vulnerability is an unknown functionality of the file /sys/class/zram-control/hot_add of the component ZRAM Kernel Module. This manipulation causes resource consumption (Kernel Memory). This vulnerability appears as CVE-2020-10781. The attack requires local access. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability has been found in Linux Kernel up to 5.8-rc5 (Operating System) and classified as problematic. Affected by this vulnerability is some unknown processing of the file /sys/class/zram-control/hot_add of the component ZRAM Kernel Module. The manipulation with an unknown input leads to a resource consumption vulnerability (Kernel Memory). The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. The summary by CVE is:
A flaw was found in the Linux Kernel before 5.8-rc6 in the ZRAM kernel module, where a user with a local account and the ability to read the /sys/class/zram-control/hot_add file can create ZRAM device nodes in the /dev/ directory. This read allocates kernel memory and is not accounted for a user that triggers the creation of that ZRAM device. With this vulnerability, continually reading the device may consume a large amount of system memory and cause the Out-of-Memory (OOM) killer to activate and terminate random userspace processes, possibly making the system inoperable.
The weakness was presented 09/16/2020 as not defined bug report (Bugzilla). The advisory is shared at bugzilla.redhat.com. This vulnerability is known as CVE-2020-10781 since 03/20/2020. An attack has to be approached locally. Required for exploitation is a single authentication. Technical details are known, but no exploit is available.
Upgrading to version 5.8-rc6 eliminates this vulnerability.
See VDB-161294 and VDB-161290 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Name: Kernel MemoryClass: Resource consumption / Kernel Memory
CWE: CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kernel 5.8-rc6
Timeline
03/20/2020 🔍09/16/2020 🔍
09/16/2020 🔍
09/16/2020 🔍
Sources
Vendor: kernel.orgAdvisory: bugzilla.redhat.com
Status: Not defined
CVE: CVE-2020-10781 (🔍)
GCVE (CVE): GCVE-0-2020-10781
GCVE (VulDB): GCVE-100-161293
See also: 🔍
Entry
Created: 09/16/2020 16:37Updated: 09/16/2020 16:42
Changes: 09/16/2020 16:37 (45), 09/16/2020 16:42 (12)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.