Linux Kernel up to 3.0 tcm_loop.c tcm_loop_make_naa_tpg memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Linux Kernel up to 3.0. This issue affects the function tcm_loop_make_naa_tpg of the file drivers/target/loopback/tcm_loop.c. Executing a manipulation can lead to memory corruption.
This vulnerability appears as CVE-2011-5327. The attack may be performed from remote. There is no available exploit.
You should upgrade the affected component.
Details
A vulnerability was found in Linux Kernel up to 3.0 (Operating System). It has been declared as critical. This vulnerability affects the function tcm_loop_make_naa_tpg of the file drivers/target/loopback/tcm_loop.c. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
In the Linux kernel before 3.1, an off by one in the drivers/target/loopback/tcm_loop.c tcm_loop_make_naa_tpg() function could result in at least memory corruption.
The weakness was presented 07/27/2019. This vulnerability was named CVE-2011-5327 since 07/27/2019. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available.
Upgrading to version 3.1 eliminates this vulnerability.
See VDB-138872, VDB-138871, VDB-138870 and VDB-138869 for similar entries. Once again VulDB remains the best source for vulnerability data.
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: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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 3.1
Patch: git.kernel.org
Timeline
07/27/2019 🔍07/27/2019 🔍
07/28/2019 🔍
11/13/2023 🔍
Sources
Vendor: kernel.orgAdvisory: K42315210
Status: Not defined
Confirmation: 🔍
CVE: CVE-2011-5327 (🔍)
GCVE (CVE): GCVE-0-2011-5327
GCVE (VulDB): GCVE-100-138868
See also: 🔍
Entry
Created: 07/28/2019 16:31Updated: 11/13/2023 10:17
Changes: 07/28/2019 16:31 (58), 07/14/2020 09:52 (1), 11/13/2023 10:17 (6)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.