BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-63829High confidence

net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink

Linux · Linux

8.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Medium, lowered one band.downgradedsince 17 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.13% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.95-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.180-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.3-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2026-63829 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink
213 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A flaw was found in the Linux kernel's IP Generic Routing Encapsulation (ip_gre) component. This vulnerability allows a local attacker with network administration capabilities in one network namespace to modify a tunnel residing in a different network namespace where they lack privileges. This is due to an insufficient capability check in the `changelink()` function, which only verifies permissions in the device's network namespace and not the tunnel's. Successful exploitation could lead to unauthorized alteration of network tunnel configurations, potentially causing network disruption or redirection of traffic.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available.
CVE-2026-63829 · CSAF 2.0 · revision 22 · interimSUSE Product Security TeamCVE-2026-63829
143 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink A tunnel changelink() operates on at most two netns, dev_net(dev) and the tunnel link netns t->net. They differ once the device is created in or moved to a netns other than the one the request runs in. The rtnl changelink path checks CAP_NET_ADMIN only against dev_net(dev), so a caller privileged there but not in t->net can rewrite a tunnel that lives in t->net. Add rtnl_dev_link_net_capable() next to rtnl_get_net_ns_capable() in net/core/rtnetlink.c. It requires CAP_NET_ADMIN in the link netns and is skipped when the link netns is dev_net(dev), where the rtnl path already checked it. The other patches in this series use the same helper. Gate ipgre_changelink() and erspan_changelink() with it, at the top of the op before any attribute is parsed, because the parsers update live tunnel fields first. ipgre_netlink_parms() sets t->collect_md before ip_tunnel_changelink() runs. Commit 8b484efd5cb4 ("ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate().") added the same check on the ioctl path. This adds it on RTM_NEWLINK.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-45495

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink A tunnel changelink() operates on at most two netns, dev_net(dev) and the tunnel link netns t->net. They differ once the device is created in or moved to a netns other than the one the request runs in. The rtnl changelink path checks CAP_NET_ADMIN only against dev_net(dev), so a caller privileged there but not in t->net can rewrite a tunnel that lives in t->net. Add rtnl_dev_link_net_capable() next to rtnl_get_net_ns_capable() in net/core/rtnetlink.c. It requires CAP_NET_ADMIN in the link netns and is skipped when the link netns is dev_net(dev), where the rtnl path already checked it. The other patches in this series use the same helper. Gate ipgre_changelink() and erspan_changelink() with it, at the top of the op before any attribute is parsed, because the parsers update live tunnel fields first. ipgre_netlink_parms() sets t->collect_md before ip_tunnel_changelink() runs. Commit 8b484efd5cb4 ("ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate().") added the same check on the ioctl path. This adds it on RTM_NEWLINK.

What

In the Linux kernel, the following vulnerability has been resolved: net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink A tunnel changelink() operates on at most two netns, dev_net(dev) and the tunnel link netns t->net. They differ once the device is created in or moved to a netns other than the one the request runs in. The rtnl changelink path checks CAP_NET_ADMIN only against dev_net(dev), so a caller privileged there but not in t->net can rewrite a tunnel that lives in t->net. Add rtnl_dev_link_net_capable() next to rtnl_get_net_ns_capable() in net/core/rtnetlink.c. It requires CAP_NET_ADMIN in the link netns and is skipped when the link netns is dev_net(dev), where the rtnl path already checked it. The other patches in this series use the same helper. Gate ipgre_changelink() and erspan_changelink() with it, at the top of the op before any attribute is parsed, because the parsers update live tunnel fields first. ipgre_netlink_parms() sets t->collect_md before ip_tunnel_changelink() runs. Commit 8b484efd5cb4 ("ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate().") added the same check on the ioctl path. This adds it on RTM_NEWLINK.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink A tunnel changelink() operates on at most two netns, dev_net(dev) and the tunnel link netns t->net. They differ once the device is created in or moved to a netns other than the one the request runs in. The rtnl changelink path checks CAP_NET_ADMIN only against dev_net(dev), so a caller privileged there but not in t->net can rewrite a tunnel that lives in t->net. Add rtnl_dev_link_net_capable() next to rtnl_get_net_ns_capable() in net/core/rtnetlink.c. It requires CAP_NET_ADMIN in the link netns and is skipped when the link netns is dev_net(dev), where the rtnl path already checked it. The other patches in this series use the same helper. Gate ipgre_changelink() and erspan_changelink() with it, at the top of the op before any attribute is parsed, because the parsers update live tunnel fields first. ipgre_netlink_parms() sets t->collect_md before ip_tunnel_changelink() runs. Commit 8b484efd5cb4 ("ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate().") added the same check on the ioctl path. This adds it on RTM_NEWLINK.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2403Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder vertrauliche Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260722Security Bulletin 22 Jul 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Jul 2026, published on 22 July 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1252Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-63820 Référence CVE CVE-2026-63821 https://www.cve.org/CVERecord?id=CVE-2026-63821 Référence CVE CVE-2026-63822 https://www.cve.org/CVERecord?id=CVE-2026-63822 Référence CVE CVE-2026-63823 https://www.cve.org/CVERecord?id=CVE-2026-63823 Référence CVE CVE-2026-63824 https://www.cve.org/CVERecord?id=CVE-2026-63824 Référence CVE CVE-2026-63825 https://www.cve.org/CVERecord?id=CVE-2026-63825 Référence CVE CVE-2026-63826 https://www.cve.org/CVERecord?id=CVE-2026-63826 Référence CVE CVE-2026-63827 https://www.cve.org/CVERecord?id=CVE-2026-63827 Référence CVE CVE-2026-63828 https://www.cve.org/CVERecord?id=CVE-2026-63828 Référence CVE CVE-2026-63829 https://www.cve.org/CVERecord?id=CVE-2026-63829 Référence CVE CVE-2026-63830 https://www.cve.org/CVERecord?id=CVE-2026-63830 Référence CVE CVE-2026-63831 https://www.cve.org/CVERecord?id=CVE-2026-63831 Référence CVE CVE-2026-63832 https://www.cve.org/CVERecord?id=CVE-2026-63832 Référence CVE CVE-2026-63833 https://www.cve.org/CVERecord?id=CVE-2026-63833 Référence CVE CVE-2026-63834 https://www.cve.org/CVERecord?id=CVE-2026-63834 Référence CVE CVE-2026-63835 https://www.cve.org/CVERecord?id=CVE-2026-63835 Référence CVE CVE-2026-63836 https://www.cve.org/CVERecord?id=CVE-2026-63836 Référence CVE CVE-2026-63837 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-63820 Référence CVE CVE-2026-63821 https://www.cve.org/CVERecord?id=CVE-2026-63821 Référence CVE CVE-2026-63822 https://www.cve.org/CVERecord?id=CVE-2026-63822 Référence CVE CVE-2026-63823 https://www.cve.org/CVERecord?id=CVE-2026-63823 Référence CVE CVE-2026-63824 https://www.cve.org/CVERecord?id=CVE-2026-63824 Référence CVE CVE-2026-63825 https://www.cve.org/CVERecord?id=CVE-2026-63825 Référence CVE CVE-2026-63826 https://www.cve.org/CVERecord?id=CVE-2026-63826 Référence CVE CVE-2026-63827 https://www.cve.org/CVERecord?id=CVE-2026-63827 Référence CVE CVE-2026-63828 https://www.cve.org/CVERecord?id=CVE-2026-63828 Référence CVE CVE-2026-63829 https://www.cve.org/CVERecord?id=CVE-2026-63829 Référence CVE CVE-2026-63830 https://www.cve.org/CVERecord?id=CVE-2026-63830 Référence CVE CVE-2026-63831 https://www.cve.org/CVERecord?id=CVE-2026-63831 Référence CVE CVE-2026-63832 https://www.cve.org/CVERecord?id=CVE-2026-63832 Référence CVE CVE-2026-63833 https://www.cve.org/CVERecord?id=CVE-2026-63833 Référence CVE CVE-2026-63834 https://www.cve.org/CVERecord?id=CVE-2026-63834 Référence CVE CVE-2026-63835 https://www.cve.org/CVERecord?id=CVE-2026-63835 Référence CVE CVE-2026-63836 https://www.cve.org/CVERecord?id=CVE-2026-63836 Référence CVE CVE-2026-63837 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1203Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-63820 Référence CVE CVE-2026-63821 https://www.cve.org/CVERecord?id=CVE-2026-63821 Référence CVE CVE-2026-63822 https://www.cve.org/CVERecord?id=CVE-2026-63822 Référence CVE CVE-2026-63823 https://www.cve.org/CVERecord?id=CVE-2026-63823 Référence CVE CVE-2026-63824 https://www.cve.org/CVERecord?id=CVE-2026-63824 Référence CVE CVE-2026-63825 https://www.cve.org/CVERecord?id=CVE-2026-63825 Référence CVE CVE-2026-63826 https://www.cve.org/CVERecord?id=CVE-2026-63826 Référence CVE CVE-2026-63827 https://www.cve.org/CVERecord?id=CVE-2026-63827 Référence CVE CVE-2026-63828 https://www.cve.org/CVERecord?id=CVE-2026-63828 Référence CVE CVE-2026-63829 https://www.cve.org/CVERecord?id=CVE-2026-63829 Référence CVE CVE-2026-63830 https://www.cve.org/CVERecord?id=CVE-2026-63830 Référence CVE CVE-2026-63831 https://www.cve.org/CVERecord?id=CVE-2026-63831 Référence CVE CVE-2026-63832 https://www.cve.org/CVERecord?id=CVE-2026-63832 Référence CVE CVE-2026-63833 https://www.cve.org/CVERecord?id=CVE-2026-63833 Référence CVE CVE-2026-63834 https://www.cve.org/CVERecord?id=CVE-2026-63834 Référence CVE CVE-2026-63835 https://www.cve.org/CVERecord?id=CVE-2026-63835 Référence CVE CVE-2026-63836 https://www.cve.org/CVERecord?id=CVE-2026-63836 Référence CVE CVE-2026-63853 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1162Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-63820 Référence CVE CVE-2026-63821 https://www.cve.org/CVERecord?id=CVE-2026-63821 Référence CVE CVE-2026-63822 https://www.cve.org/CVERecord?id=CVE-2026-63822 Référence CVE CVE-2026-63823 https://www.cve.org/CVERecord?id=CVE-2026-63823 Référence CVE CVE-2026-63824 https://www.cve.org/CVERecord?id=CVE-2026-63824 Référence CVE CVE-2026-63825 https://www.cve.org/CVERecord?id=CVE-2026-63825 Référence CVE CVE-2026-63826 https://www.cve.org/CVERecord?id=CVE-2026-63826 Référence CVE CVE-2026-63827 https://www.cve.org/CVERecord?id=CVE-2026-63827 Référence CVE CVE-2026-63828 https://www.cve.org/CVERecord?id=CVE-2026-63828 Référence CVE CVE-2026-63829 https://www.cve.org/CVERecord?id=CVE-2026-63829 Référence CVE CVE-2026-63830 https://www.cve.org/CVERecord?id=CVE-2026-63830 Référence CVE CVE-2026-63831 https://www.cve.org/CVERecord?id=CVE-2026-63831 Référence CVE CVE-2026-63832 https://www.cve.org/CVERecord?id=CVE-2026-63832 Référence CVE CVE-2026-63833 https://www.cve.org/CVERecord?id=CVE-2026-63833 Référence CVE CVE-2026-63834 https://www.cve.org/CVERecord?id=CVE-2026-63834 Référence CVE CVE-2026-63835 https://www.cve.org/CVERecord?id=CVE-2026-63835 Référence CVE CVE-2026-63836 https://www.cve.org/CVERecord?id=CVE-2026-63836 Référence CVE CVE-2026-63837 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1091Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-63795 Référence CVE CVE-2026-63802 https://www.cve.org/CVERecord?id=CVE-2026-63802 Référence CVE CVE-2026-63806 https://www.cve.org/CVERecord?id=CVE-2026-63806 Référence CVE CVE-2026-63807 https://www.cve.org/CVERecord?id=CVE-2026-63807 Référence CVE CVE-2026-63809 https://www.cve.org/CVERecord?id=CVE-2026-63809 Référence CVE CVE-2026-63821 https://www.cve.org/CVERecord?id=CVE-2026-63821 Référence CVE CVE-2026-63822 https://www.cve.org/CVERecord?id=CVE-2026-63822 Référence CVE CVE-2026-63824 https://www.cve.org/CVERecord?id=CVE-2026-63824 Référence CVE CVE-2026-63826 https://www.cve.org/CVERecord?id=CVE-2026-63826 Référence CVE CVE-2026-63829 https://www.cve.org/CVERecord?id=CVE-2026-63829 Référence CVE CVE-2026-63836 https://www.cve.org/CVERecord?id=CVE-2026-63836 Référence CVE CVE-2026-63843 https://www.cve.org/CVERecord?id=CVE-2026-63843 Référence CVE CVE-2026-63844 https://www.cve.org/CVERecord?id=CVE-2026-63844 Référence CVE CVE-2026-63845 https://www.cve.org/CVERecord?id=CVE-2026-63845 Référence CVE CVE-2026-63846 https://www.cve.org/CVERecord?id=CVE-2026-63846 Référence CVE CVE-2026-63847 https://www.cve.org/CVERecord?id=CVE-2026-63847 Référence CVE CVE-2026-63848 https://www.cve.org/CVERecord?id=CVE-2026-63848 Référence CVE CVE-2026-63851 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1064Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-63802 Référence CVE CVE-2026-63806 https://www.cve.org/CVERecord?id=CVE-2026-63806 Référence CVE CVE-2026-63807 https://www.cve.org/CVERecord?id=CVE-2026-63807 Référence CVE CVE-2026-63809 https://www.cve.org/CVERecord?id=CVE-2026-63809 Référence CVE CVE-2026-63821 https://www.cve.org/CVERecord?id=CVE-2026-63821 Référence CVE CVE-2026-63822 https://www.cve.org/CVERecord?id=CVE-2026-63822 Référence CVE CVE-2026-63824 https://www.cve.org/CVERecord?id=CVE-2026-63824 Référence CVE CVE-2026-63826 https://www.cve.org/CVERecord?id=CVE-2026-63826 Référence CVE CVE-2026-63827 https://www.cve.org/CVERecord?id=CVE-2026-63827 Référence CVE CVE-2026-63829 https://www.cve.org/CVERecord?id=CVE-2026-63829 Référence CVE CVE-2026-63831 https://www.cve.org/CVERecord?id=CVE-2026-63831 Référence CVE CVE-2026-63836 https://www.cve.org/CVERecord?id=CVE-2026-63836 Référence CVE CVE-2026-63842 https://www.cve.org/CVERecord?id=CVE-2026-63842 Référence CVE CVE-2026-63843 https://www.cve.org/CVERecord?id=CVE-2026-63843 Référence CVE CVE-2026-63844 https://www.cve.org/CVERecord?id=CVE-2026-63844 Référence CVE CVE-2026-63845 https://www.cve.org/CVERecord?id=CVE-2026-63845 Référence CVE CVE-2026-63846 https://www.cve.org/CVERecord?id=CVE-2026-63846 Référence CVE CVE-2026-63847 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1031Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-53399 Référence CVE CVE-2026-53400 https://www.cve.org/CVERecord?id=CVE-2026-53400 Référence CVE CVE-2026-53402 https://www.cve.org/CVERecord?id=CVE-2026-53402 Référence CVE CVE-2026-63797 https://www.cve.org/CVERecord?id=CVE-2026-63797 Référence CVE CVE-2026-63806 https://www.cve.org/CVERecord?id=CVE-2026-63806 Référence CVE CVE-2026-63810 https://www.cve.org/CVERecord?id=CVE-2026-63810 Référence CVE CVE-2026-63815 https://www.cve.org/CVERecord?id=CVE-2026-63815 Référence CVE CVE-2026-63816 https://www.cve.org/CVERecord?id=CVE-2026-63816 Référence CVE CVE-2026-63818 https://www.cve.org/CVERecord?id=CVE-2026-63818 Référence CVE CVE-2026-63829 https://www.cve.org/CVERecord?id=CVE-2026-63829 Référence CVE CVE-2026-63970 https://www.cve.org/CVERecord?id=CVE-2026-63970 Référence CVE CVE-2026-64187 https://www.cve.org/CVERecord?id=CVE-2026-64187 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=CVE-2026-64189 Référence CVE CVE-2026-64192 https://www.cve.org/CVERecord?id=CVE-2026-64192 Référence CVE CVE-2026-64206 https://www.cve.org/CVERecord?id=CVE-2026-64206 Référence CVE CVE-2026-64227 https://www.cve.org/CVERecord?id=CVE-2026-64227 Référence CVE CVE-2026-64241 https://www.cve.org/CVERecord?id=CVE-2026-64241 Référence CVE CVE-2026-64248 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1029Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-53397 Référence CVE CVE-2026-53399 https://www.cve.org/CVERecord?id=CVE-2026-53399 Référence CVE CVE-2026-53402 https://www.cve.org/CVERecord?id=CVE-2026-53402 Référence CVE CVE-2026-63794 https://www.cve.org/CVERecord?id=CVE-2026-63794 Référence CVE CVE-2026-63802 https://www.cve.org/CVERecord?id=CVE-2026-63802 Référence CVE CVE-2026-63806 https://www.cve.org/CVERecord?id=CVE-2026-63806 Référence CVE CVE-2026-63807 https://www.cve.org/CVERecord?id=CVE-2026-63807 Référence CVE CVE-2026-63824 https://www.cve.org/CVERecord?id=CVE-2026-63824 Référence CVE CVE-2026-63826 https://www.cve.org/CVERecord?id=CVE-2026-63826 Référence CVE CVE-2026-63829 https://www.cve.org/CVERecord?id=CVE-2026-63829 Référence CVE CVE-2026-63884 https://www.cve.org/CVERecord?id=CVE-2026-63884 Référence CVE CVE-2026-63893 https://www.cve.org/CVERecord?id=CVE-2026-63893 Référence CVE CVE-2026-63899 https://www.cve.org/CVERecord?id=CVE-2026-63899 Référence CVE CVE-2026-63901 https://www.cve.org/CVERecord?id=CVE-2026-63901 Référence CVE CVE-2026-63912 https://www.cve.org/CVERecord?id=CVE-2026-63912 Référence CVE CVE-2026-63915 https://www.cve.org/CVERecord?id=CVE-2026-63915 Référence CVE CVE-2026-63917 https://www.cve.org/CVERecord?id=CVE-2026-63917 Référence CVE CVE-2026-63919 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0982Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-63810 Référence CVE CVE-2026-63814 https://www.cve.org/CVERecord?id=CVE-2026-63814 Référence CVE CVE-2026-63815 https://www.cve.org/CVERecord?id=CVE-2026-63815 Référence CVE CVE-2026-63818 https://www.cve.org/CVERecord?id=CVE-2026-63818 Référence CVE CVE-2026-63822 https://www.cve.org/CVERecord?id=CVE-2026-63822 Référence CVE CVE-2026-63823 https://www.cve.org/CVERecord?id=CVE-2026-63823 Référence CVE CVE-2026-63824 https://www.cve.org/CVERecord?id=CVE-2026-63824 Référence CVE CVE-2026-63827 https://www.cve.org/CVERecord?id=CVE-2026-63827 Référence CVE CVE-2026-63828 https://www.cve.org/CVERecord?id=CVE-2026-63828 Référence CVE CVE-2026-63829 https://www.cve.org/CVERecord?id=CVE-2026-63829 Référence CVE CVE-2026-63830 https://www.cve.org/CVERecord?id=CVE-2026-63830 Référence CVE CVE-2026-63831 https://www.cve.org/CVERecord?id=CVE-2026-63831 Référence CVE CVE-2026-63834 https://www.cve.org/CVERecord?id=CVE-2026-63834 Référence CVE CVE-2026-63835 https://www.cve.org/CVERecord?id=CVE-2026-63835 Référence CVE CVE-2026-63836 https://www.cve.org/CVERecord?id=CVE-2026-63836 Référence CVE CVE-2026-64187 https://www.cve.org/CVERecord?id=CVE-2026-64187 Référence CVE CVE-2026-64188 https://www.cve.org/CVERecord?id=CVE-2026-64188 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 19 Jul 2026 · Last source change 17 Aug 2026, 04:51 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-45495
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD awaiting enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-63829 to remediation: access.redhat.com/CVE-2026-63829.
    Before
    remediation: access.redhat.com/CVE-2026-63829
    After
    remediation: access.redhat.com/CVE-2026-63829
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Mitigation available to Patch available.
    Before
    Mitigation available
    After
    Patch available
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    kernel as a component of Red Hat Enterprise Linux 10; kernel-64k as a component of Red Hat Enterprise Linux 10; kernel-64k-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-64k-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 230 more
    After
    kernel as a component of Red Hat Enterprise Linux 10; kernel-64k as a component of Red Hat Enterprise Linux 10; kernel-64k-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-64k-devel as a component of Red Hat Enterprise Linux 10; kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-64k-modules as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-core as a component of Red Hat Enterprise Linux 10; kernel-64k-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-abi-stablelists as a component of Red Hat Enterprise Linux 10; kernel-core as a component of Red Hat Enterprise Linux 10; kernel-debug as a component of Red Hat Enterprise Linux 10; kernel-debug-core as a component of Red Hat Enterprise Linux 10; kernel-debug-devel as a component of Red Hat Enterprise Linux 10; kernel-debug-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-debug-modules as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-core as a component of Red Hat Enterprise Linux 10; kernel-debug-modules-extra as a component of Red Hat Enterprise Linux 10; kernel-debug-uki-virt as a component of Red Hat Enterprise Linux 10; kernel-devel as a component of Red Hat Enterprise Linux 10; kernel-devel-matched as a component of Red Hat Enterprise Linux 10; kernel-doc as a component of Red Hat Enterprise Linux 10; kernel-modules as a component of Red Hat Enterprise Linux 10; kernel-modules-core as a component of Red Hat Enterprise Linux 10; and 183 more · Fixed: bpftool-0:4.18.0-553.171.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.171.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.171.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-0:4.18.0-553.171.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.171.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.171.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.171.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); bpftool-debuginfo-0:4.18.0-553.171.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.171.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.171.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.171.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.171.1.el8_10.src as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-0:4.18.0-553.171.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-abi-stablelists-0:4.18.0-553.171.1.el8_10.noarch as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.171.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.171.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.171.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-core-0:4.18.0-553.171.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.171.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.171.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.171.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-0:4.18.0-553.171.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.171.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.171.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.171.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-core-0:4.18.0-553.171.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.171.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.171.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.171.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8); kernel-debug-debuginfo-0:4.18.0-553.171.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8); and 120 more
    Red Hat Product Security ↗
  4. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-63829 to remediation: access.redhat.com/CVE-2026-63829.
    Before
    remediation: access.redhat.com/CVE-2026-63829
    After
    remediation: access.redhat.com/CVE-2026-63829
    Red Hat Product Security ↗
  5. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-45495↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-63829 · cve.blacktree.nl