Linux Kernel 3.14-rc kernel/sched/core.c sched_read_attr information disclosure

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Linux Kernel 3.14-rc and classified as problematic. Impacted is the function sched_read_attr of the file kernel/sched/core.c. This manipulation causes information disclosure.
This vulnerability is tracked as CVE-2014-9903. The attack is restricted to local execution. No exploit exists.
Details
A vulnerability has been found in Linux Kernel 3.14-rc (Operating System) and classified as problematic. Affected by this vulnerability is the function sched_read_attr of the file kernel/sched/core.c. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
The sched_read_attr function in kernel/sched/core.c in the Linux kernel 3.14-rc before 3.14-rc4 uses an incorrect size, which allows local users to obtain sensitive information from kernel stack memory via a crafted sched_getattr system call.
The weakness was disclosed 06/27/2016 (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2014-9903 since 06/24/2016. The exploitation appears to be easy. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 91511†). The entry VDB-90546 is pretty similar. 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.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Patch: git.kernel.org
Timeline
06/24/2016 🔍06/27/2016 🔍
06/27/2016 🔍
06/29/2016 🔍
08/25/2022 🔍
Sources
Vendor: kernel.orgAdvisory: 4efbc454ba68def5ef285b26ebfcfdb605b52755⛔
Status: Not defined
Confirmation: 🔍
CVE: CVE-2014-9903 (🔍)
GCVE (CVE): GCVE-0-2014-9903
GCVE (VulDB): GCVE-100-88357
SecurityFocus: 91511 - Linux Kernel CVE-2014-9903 Local Information Disclosure Vulnerability
See also: 🔍
Entry
Created: 06/29/2016 11:17Updated: 08/25/2022 10:33
Changes: 06/29/2016 11:17 (47), 02/12/2019 10:30 (15), 08/25/2022 10:33 (3)
Complete: 🔍
Cache ID: 216:9B4: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.