Metrics
Affected Vendors & Products
Tue, 04 Aug 2026 10:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
cvssV3_1
|
Sat, 16 Nov 2024 02:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-119 |
Sun, 29 Sep 2024 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 19 Sep 2024 14:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Linux
Linux linux Kernel |
|
| Weaknesses | CWE-476 | |
| CPEs | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Linux
Linux linux Kernel |
Fri, 13 Sep 2024 23:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Fri, 13 Sep 2024 06:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In the Linux kernel, the following vulnerability has been resolved: drm/xe: reset mmio mappings with devm Set our various mmio mappings to NULL. This should make it easier to catch something rogue trying to mess with mmio after device removal. For example, we might unmap everything and then start hitting some mmio address which has already been unmamped by us and then remapped by something else, causing all kinds of carnage. | |
| Title | drm/xe: reset mmio mappings with devm | |
| References |
|
Status: PUBLISHED
Assigner: Linux
Published:
Updated: 2026-08-04T09:31:22.092Z
Reserved: 2024-09-11T15:12:18.251Z
Link: CVE-2024-46705
Updated: 2024-09-29T15:03:12.238Z
Status : Analyzed
Published: 2024-09-13T07:15:05.477
Modified: 2026-06-17T07:55:45.910
Link: CVE-2024-46705
OpenCVE Enrichment
No data.