Linux Kernel up to 5.11.8 Thread fs/io_uring.c deadlock

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Linux Kernel up to 5.11.8 and classified as problematic. Impacted is an unknown function of the file fs/io_uring.c of the component Thread Handler. This manipulation causes deadlock. This vulnerability is tracked as CVE-2021-28951. No exploit exists. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability has been found in Linux Kernel up to 5.11.8 (Operating System) and classified as problematic. Affected by this vulnerability is an unknown part of the file fs/io_uring.c of the component Thread Handler. The manipulation with an unknown input leads to a deadlock vulnerability. The CWE definition for the vulnerability is CWE-833. The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock. As an impact it is known to affect availability.
The weakness was disclosed 03/21/2021. The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2021-28951. Technical details are known, but no exploit is available.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.kernel.org.
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: 4.5VulDB Meta Temp Score: 4.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.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: DeadlockCWE: CWE-833 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Partially
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: git.kernel.org
Timeline
03/20/2021 🔍03/21/2021 🔍
03/21/2021 🔍
04/03/2021 🔍
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Not defined
CVE: CVE-2021-28951 (🔍)
GCVE (CVE): GCVE-0-2021-28951
GCVE (VulDB): GCVE-100-171517
Entry
Created: 03/21/2021 07:52Updated: 04/03/2021 13:07
Changes: 03/21/2021 07:52 (41), 04/03/2021 13:02 (2), 04/03/2021 13:07 (18)
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.