CVE-2026-43486: Kernel Contpte Fault in Linux Kernel
Plattform
linux
Komponente
linux
Behoben in
97c5550b763171dbef61e6239cab372b9f9cd4a2
CVE-2026-43486 addresses a vulnerability within the Linux Kernel's contpte subsystem. This flaw involves an incorrect check within the setaccessflags() function, potentially leading to incorrect access flag handling and bypassing hardware-enforced restrictions. The vulnerability impacts Linux Kernel versions prior to 97c5550b763171dbef61e6239cab372b9f9cd4a2, and a fix is available in the specified version.
Auswirkungen und Angriffsszenarien
The vulnerability lies in the contpteptepsetaccessflags() function, which incorrectly handles access flags when dealing with hardware faults. Specifically, the function compares the gathered PTEP value against the requested entry, but due to how ptepget() operates, a dirty sibling PTE can cause the target to appear already-dirty, even if it still has PTERDONLY set in hardware. This misinterpretation could allow an attacker to bypass access restrictions and potentially read or write to memory locations they shouldn't have access to. While the description mentions FEAT_HAFDBS, the core issue affects systems regardless of this feature's presence, as the flawed logic is still present. The potential impact is privilege escalation and unauthorized data access.
Ausnutzungskontext
CVE-2026-43486 was published on 2026-05-13. Its exploitation context is currently limited due to the recent publication date. It is not currently listed on KEV or EPSS, indicating a low to medium probability of exploitation. No public proof-of-concept exploits are currently known. Monitor security advisories and threat intelligence feeds for any indications of active exploitation campaigns.
Bedrohungsanalyse
Exploit-Status
EPSS
0.02% (5% Perzentil)
Betroffene Software
Zeitleiste
- Reserviert
- Veröffentlicht
- EPSS aktualisiert
Mitigation und Workarounds
The primary mitigation for CVE-2026-43486 is to upgrade the Linux Kernel to version 97c5550b763171dbef61e6239cab372b9f9cd4a2 or later. If an immediate upgrade is not feasible due to compatibility concerns or testing requirements, consider applying relevant patches from your distribution vendor. While a direct workaround isn't available, ensuring the kernel is running the latest stable release is crucial. Monitor kernel update announcements from your distribution for timely patching. After upgrading, confirm the fix by verifying access control mechanisms and reviewing system logs for any unusual activity.
So behebenwird übersetzt…
Aplicar la actualización del kernel a la versión 6.9 o superior. Esta actualización corrige un error en el manejo de las señales de fallo de la SMMU/ATS, evitando un posible bucle infinito de fallos en ciertas configuraciones de hardware.
Häufig gestellte Fragen
What is CVE-2026-43486 — Kernel Contpte Fault in Linux Kernel?
CVE-2026-43486 is a vulnerability in the Linux Kernel's contpte subsystem that can lead to incorrect access flag handling, potentially bypassing access restrictions. It affects versions prior to 97c5550b763171dbef61e6239cab372b9f9cd4a2.
Am I affected by CVE-2026-43486 in Linux Kernel?
You are affected if your Linux Kernel version is less than or equal to 97c5550b763171dbef61e6239cab372b9f9cd4a2. Check your kernel version using 'uname -r'.
How do I fix CVE-2026-43486 in Linux Kernel?
Upgrade your Linux Kernel to version 97c5550b763171dbef61e6239cab372b9f9cd4a2 or later. Consult your distribution's documentation for upgrade instructions.
Is CVE-2026-43486 being actively exploited?
Currently, there are no known public exploits or active campaigns targeting CVE-2026-43486, but monitoring is advised due to its recent publication.
Where can I find the official Linux advisory for CVE-2026-43486?
Refer to the Linux Kernel mailing list archives and your distribution's security advisories for official information regarding CVE-2026-43486.
Ist dein Projekt betroffen?
Lade deine Abhängigkeitsdatei hoch und erfahre sofort, ob dich diese und andere CVEs treffen.
Jetzt testen — kein Konto
Laden Sie ein beliebiges Manifest hoch (composer.lock, package-lock.json, WordPress-Plugin-Liste…) oder fügen Sie Ihre Komponentenliste ein. Sie erhalten sofort einen Schwachstellenbericht. Das Hochladen einer Datei ist nur der Anfang: Mit einem Konto erhalten Sie kontinuierliche Überwachung, Slack/E-Mail-Benachrichtigungen, mehrere Projekte und White-Label-Berichte.
Abhängigkeitsdatei hier ablegen
composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...