CVE-2026-63879·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix amdgpu_hmm_range_get_pages The notifier sequence must only be read once or otherwise we could work with invalid pages. While at it also fix the coding style, e.g. drop the pre-initialized return value and use the common define for 2G range. (cherry picked from commit c08972f555945cda57b0adb72272a37910153390)
- Severity
- high
- Software
- Kernel
- Fixed in
- 7.0.12
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.14% — higher than 4% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-63879 scores 7.8 on CVSS, so a successful attack would be serious — but at 0.14%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 7.0.12
Fixed in: 7.0.12
How to fix this CVE
Update your Linux kernel to version 7.0.12 or later to resolve this memory management vulnerability in the AMD GPU driver. This patch corrects a critical race condition in the HMM range page retrieval function that could allow privileged local attackers to access or modify sensitive memory. Apply the update immediately to systems running kernel versions 6.19 through 7.0.11.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your kernel version with `uname -r` and verify if it falls within the 6.19 to 7.0.11 range.
- Step 2: Confirm AMD GPU driver is in use by running `lspci | grep -i amd` and checking for AMDGPU devices.
- Step 3: Search kernel logs for HMM-related memory faults using `dmesg | grep -i 'hmm\|amdgpu.*error'` to identify potential exploitation attempts.
- Step 4: After updating, verify the fix with `uname -r` to confirm kernel version is now 7.0.12 or later, then reboot if necessary.
FAQ
What is CVE-2026-63879?
This vulnerability exists in the AMD GPU (AMDGPU) driver's HMM (Heterogeneous Memory Management) range handler, where the notifier sequence counter could be read multiple times during page retrieval, leading to potential access to stale or invalid memory pages with elevated privileges.
Is CVE-2026-63879 being actively exploited?
No, this vulnerability is not currently being actively exploited in the wild according to CISA records, and no public exploit code has been released.
What versions of Kernel are affected by CVE-2026-63879?
Linux kernel versions 6.19 through 7.0.11 are affected; version 7.0.12 and later contain the fix.
How do I check if my server is vulnerable to CVE-2026-63879?
Run `uname -r` to display your kernel version—if it shows 6.19 through 7.0.11 and you have AMDGPU devices (verify with `lspci | grep AMD`), your system is vulnerable and requires immediate updating.
Does Defensia detect CVE-2026-63879?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2026-63879 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/2fd24407457a6b181ba827705678da70e528dcd0
- https://git.kernel.org/stable/c/93a9f121de6383f20290840d025ee28fda5f53b5
- https://git.kernel.org/stable/c/962d684b5dc0741dcd93485d41b450de402d5592
- https://git.kernel.org/stable/c/e35cf322897dd4921248d11311a89c865b534c14
- https://git.kernel.org/stable/c/fa34d3e14cb763b50702e8a0f7d4cfd877a73ab9
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-63879. Free for 1 server.
Get started free