Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2024-56669 | First vendor Publication | 2024-12-27 |
Vendor | Cve | Last vendor Modification | 2025-02-11 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | |||
---|---|---|---|
Overall CVSS Score | 7.8 | ||
Base Score | 7.8 | Environmental Score | 7.8 |
impact SubScore | 5.9 | Temporal Score | 7.8 |
Exploitabality Sub Score | 1.8 | ||
Attack Vector | Local | Attack Complexity | Low |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | High |
Integrity Impact | High | 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: iommu/vt-d: Remove cache tags before disabling ATS The current implementation removes cache tags after disabling ATS, leading to potential memory leaks and kernel crashes. Specifically, CACHE_TAG_DEVTLB type cache tags may still remain in the list even after the domain is freed, causing a use-after-free condition. This issue really shows up when multiple VFs from different PFs passed through to a single user-space process via vfio-pci. In such cases, the kernel may crash with kernel messages like: BUG: kernel NULL pointer dereference, address: 0000000000000014 Move cache_tag_unassign_domain() before iommu_disable_pci_caps() to fix it. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-56669 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
33 % | CWE-476 | NULL Pointer Dereference |
33 % | CWE-416 | Use After Free |
33 % | CWE-401 | Failure to Release Memory Before Removing Last Reference ('Memory Leak') |
CPE : Common Platform Enumeration
Sources (Detail)
Source | Url |
---|
Alert History
Date | Informations |
---|---|
2025-07-15 02:41:15 |
|
2025-07-14 12:38:33 |
|
2025-06-26 02:38:30 |
|
2025-06-25 12:36:34 |
|
2025-06-24 02:43:08 |
|
2025-05-27 02:48:33 |
|
2025-03-29 03:44:27 |
|
2025-03-28 13:47:43 |
|
2025-03-28 03:22:16 |
|
2025-03-19 03:17:05 |
|
2025-03-18 03:30:04 |
|
2025-03-14 03:17:11 |
|
2025-03-06 14:13:44 |
|
2025-02-22 03:27:16 |
|
2025-02-11 21:20:53 |
|
2025-01-08 00:20:54 |
|
2025-01-07 03:08:09 |
|
2025-01-07 00:20:36 |
|
2025-01-06 21:20:45 |
|
2024-12-27 21:20:27 |
|