Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2022-49549 | First vendor Publication | 2025-02-26 |
| Vendor | Cve | Last vendor Modification | 2025-03-10 |
Security-Database Scoring CVSS v3
| Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | |||
|---|---|---|---|
| Overall CVSS Score | 5.5 | ||
| Base Score | 5.5 | Environmental Score | 5.5 |
| impact SubScore | 3.6 | Temporal Score | 5.5 |
| Exploitabality Sub Score | 1.8 | ||
| Attack Vector | Local | Attack Complexity | Low |
| Privileges Required | Low | User Interaction | None |
| Scope | Unchanged | Confidentiality Impact | None |
| Integrity Impact | None | Availability Impact | High |
| Calculate full CVSS 3.0 Vectors scores | |||
Security-Database Scoring CVSS v2
| Cvss vector : | |||
|---|---|---|---|
| Cvss Base Score | N/A | Attack Range | N/A |
| Cvss Impact Score | N/A | Attack Complexity | N/A |
| Cvss Expoit Score | N/A | Authentication | N/A |
| Calculate full CVSS 2.0 Vectors scores | |||
Detail
| In the Linux kernel, the following vulnerability has been resolved: x86/MCE/AMD: Fix memory leak when threshold_create_bank() fails In mce_threshold_create_device(), if threshold_create_bank() fails, the previously allocated threshold banks array @bp will be leaked because the call to mce_threshold_remove_device() will not free it. This happens because mce_threshold_remove_device() fetches the pointer through the threshold_banks per-CPU variable but bp is written there only after the bank creation is successful, and not before, when threshold_create_bank() fails. Add a helper which unwinds all the bank creation work previously done and pass into it the previously allocated threshold banks array for freeing. [ bp: Massage. ] |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-49549 |
CWE : Common Weakness Enumeration
| % | Id | Name |
|---|---|---|
| 100 % | CWE-401 | Failure to Release Memory Before Removing Last Reference ('Memory Leak') |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2025-06-26 02:09:56 |
|
| 2025-06-25 12:22:46 |
|
| 2025-06-24 02:14:31 |
|
| 2025-05-27 02:11:17 |
|
| 2025-03-29 03:14:50 |
|
| 2025-03-28 13:35:10 |
|
| 2025-03-28 02:57:14 |
|
| 2025-03-19 00:20:55 |
|
| 2025-03-18 00:20:58 |
|
| 2025-03-14 00:21:27 |
|
| 2025-03-13 21:21:19 |
|
| 2025-03-11 00:21:22 |
|
| 2025-02-26 17:20:30 |
|
