BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-45878High confidence

drm/amdkfd: Fix watch_id bounds checking in debug address watch v2

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

20 package states
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.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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 record ↗Source updated 10 Sept 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.

1 current
CVE-2026-45878 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: drm/amdkfd: Fix watch_id bounds checking in debug address watch v2
22 known affected

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

  • kernel-rt as a component of Red Hat Enterprise Linux 9
  • kernel-rt-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9
Summary
A flaw was found in the Linux kernel's AMD KFD (Kernel Fusion Driver) component. A local user could exploit a boundary error in the debug address watch v2 functionality by providing a specially crafted watch_id. This could lead to a buffer overflow, potentially allowing memory access outside of intended bounds and causing system instability or denial of service.
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.
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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-32344

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 actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix watch_id bounds checking in debug address watch v2 The address watch clear code receives watch_id as an unsigned value (u32), but some helper functions were using a signed int and checked bits by shifting with watch_id. If a very large watch_id is passed from userspace, it can be converted to a negative value. This can cause invalid shifts and may access memory outside the watch_points array. drm/amdkfd: Fix watch_id bounds checking in debug address watch v2 Fix this by checking that watch_id is within MAX_WATCH_ADDRESSES before using it. Also use BIT(watch_id) to test and clear bits safely. This keeps the behavior unchanged for valid watch IDs and avoids undefined behavior for invalid ones. Fixes the below: drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_debug.c:448 kfd_dbg_trap_clear_dev_address_watch() error: buffer overflow 'pdd->watch_points' 4 <= u32max user_rl='0-3,2147483648-u32max' uncapped drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_debug.c 433 int kfd_dbg_trap_clear_dev_address_watch(struct kfd_process_device *pdd, 434 uint32_t watch_id) 435 { 436 int r; 437 438 if (!kfd_dbg_owns_dev_watch_id(pdd, watch_id)) kfd_dbg_owns_dev_watch_id() doesn't check for negative values so if watch_id is larger than INT_MAX it leads to a buffer overflow. (Negative shifts are undefined). 439 return -EINVAL; 440 441 if (!pdd->dev->kfd->shared_resources.enable_mes) { 442 r = debug_lock_and_unmap(pdd->dev->dqm); 443 if (r) 444 return r; 445 } 446 447 amdgpu_gfx_off_ctrl(pdd->dev->adev, false); --> 448 pdd->watch_points[watch_id] = pdd->dev->kfd2kgd->clear_address_watch( 449 pdd->dev->adev, 450 watch_id); v2: (as per, Jonathan Kim) - Add early watch_id >= MAX_WATCH_ADDRESSES validation in the set path to match the clear path. - Drop the redundant bounds check in kfd_dbg_owns_dev_watch_id().

What

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix watch_id bounds checking in debug address watch v2 The address watch clear code receives watch_id as an unsigned value (u32), but some helper functions were using a signed int and checked bits by shifting with watch_id. If a very large watch_id is passed from userspace, it can be converted to a negative value. This can cause invalid shifts and may access memory outside the watch_points array. drm/amdkfd: Fix watch_id bounds checking in debug address watch v2 Fix this by checking that watch_id is within MAX_WATCH_ADDRESSES before using it. Also use BIT(watch_id) to test and clear bits safely. This keeps the behavior unchanged for valid watch IDs and avoids undefined behavior for invalid ones. Fixes the below: drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_debug.c:448 kfd_dbg_trap_clear_dev_address_watch() error: buffer overflow 'pdd->watch_points' 4 <= u32max user_rl='0-3,2147483648-u32max' uncapped drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_debug.c 433 int kfd_dbg_trap_clear_dev_address_watch(struct kfd_process_device *pdd, 434 uint32_t watch_id) 435 { 436 int r; 437 438 if (!kfd_dbg_owns_dev_watch_id(pdd, watch_id)) kfd_dbg_owns_dev_watch_id() doesn't check for negative values so if watch_id is larger than INT_MAX it leads to a buffer overflow. (Negative shifts are undefined). 439 return -EINVAL; 440 441 if (!pdd->dev->kfd->shared_resources.enable_mes) { 442 r = debug_lock_and_unmap(pdd->dev->dqm); 443 if (r) 444 return r; 445 } 446 447 amdgpu_gfx_off_ctrl(pdd->dev->adev, false); --> 448 pdd->watch_points[watch_id] = pdd->dev->kfd2kgd->clear_address_watch( 449 pdd->dev->adev, 450 watch_id); v2: (as per, Jonathan Kim) - Add early watch_id >= MAX_WATCH_ADDRESSES validation in the set path to match the clear path. - Drop the redundant bounds check in kfd_dbg_owns_dev_watch_id().

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: drm/amdkfd: Fix watch_id bounds checking in debug address watch v2 The address watch clear code receives watch_id as an unsigned value (u32), but some helper functions were using a signed int and checked bits by shifting with watch_id. If a very large watch_id is passed from userspace, it can be converted to a negative value. This can cause invalid shifts and may access memory outside the watch_points array. drm/amdkfd: Fix watch_id bounds checking in debug address watch v2 Fix this by checking that watch_id is within MAX_WATCH_ADDRESSES before using it. Also use BIT(watch_id) to test and clear bits safely. This keeps the behavior unchanged for valid watch IDs and avoids undefined behavior for invalid ones. Fixes the below: drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_debug.c:448 kfd_dbg_trap_clear_dev_address_watch() error: buffer overflow 'pdd->watch_points' 4 <= u32max user_rl='0-3,2147483648-u32max' uncapped drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_debug.c 433 int kfd_dbg_trap_clear_dev_address_watch(struct kfd_process_device *pdd, 434 uint32_t watch_id) 435 { 436 int r; 437 438 if (!kfd_dbg_owns_dev_watch_id(pdd, watch_id)) kfd_dbg_owns_dev_watch_id() doesn't check for negative values so if watch_id is larger than INT_MAX it leads to a buffer overflow. (Negative shifts are undefined). 439 return -EINVAL; 440 441 if (!pdd->dev->kfd->shared_resources.enable_mes) { 442 r = debug_lock_and_unmap(pdd->dev->dqm); 443 if (r) 444 return r; 445 } 446 447 amdgpu_gfx_off_ctrl(pdd->dev->adev, false); --> 448 pdd->watch_points[watch_id] = pdd->dev->kfd2kgd->clear_address_watch( 449 pdd->dev->adev, 450 watch_id); v2: (as per, Jonathan Kim) - Add early watch_id >= MAX_WATCH_ADDRESSES validation in the set path to match the clear path. - Drop the redundant bounds check in kfd_dbg_owns_dev_watch_id().

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
Unchanged: impact remains within the vulnerable component's 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:U/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.SUnchangedScope: The security impact remains within the vulnerable component's 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-W-2026-1700Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.

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

d?id=CVE-2026-45867 Référence CVE CVE-2026-45868 https://www.cve.org/CVERecord?id=CVE-2026-45868 Référence CVE CVE-2026-45869 https://www.cve.org/CVERecord?id=CVE-2026-45869 Référence CVE CVE-2026-45871 https://www.cve.org/CVERecord?id=CVE-2026-45871 Référence CVE CVE-2026-45872 https://www.cve.org/CVERecord?id=CVE-2026-45872 Référence CVE CVE-2026-45873 https://www.cve.org/CVERecord?id=CVE-2026-45873 Référence CVE CVE-2026-45874 https://www.cve.org/CVERecord?id=CVE-2026-45874 Référence CVE CVE-2026-45875 https://www.cve.org/CVERecord?id=CVE-2026-45875 Référence CVE CVE-2026-45877 https://www.cve.org/CVERecord?id=CVE-2026-45877 Référence CVE CVE-2026-45878 https://www.cve.org/CVERecord?id=CVE-2026-45878 Référence CVE CVE-2026-45879 https://www.cve.org/CVERecord?id=CVE-2026-45879 Référence CVE CVE-2026-45880 https://www.cve.org/CVERecord?id=CVE-2026-45880 Référence CVE CVE-2026-45881 https://www.cve.org/CVERecord?id=CVE-2026-45881 Référence CVE CVE-2026-45882 https://www.cve.org/CVERecord?id=CVE-2026-45882 Référence CVE CVE-2026-45883 https://www.cve.org/CVERecord?id=CVE-2026-45883 Référence CVE CVE-2026-45885 https://www.cve.org/CVERecord?id=CVE-2026-45885 Référence CVE CVE-2026-45895 https://www.cve.org/CVERecord?id=CVE-2026-45895 Référence CVE CVE-2026-45900 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45867 Référence CVE CVE-2026-45868 https://www.cve.org/CVERecord?id=CVE-2026-45868 Référence CVE CVE-2026-45869 https://www.cve.org/CVERecord?id=CVE-2026-45869 Référence CVE CVE-2026-45870 https://www.cve.org/CVERecord?id=CVE-2026-45870 Référence CVE CVE-2026-45871 https://www.cve.org/CVERecord?id=CVE-2026-45871 Référence CVE CVE-2026-45872 https://www.cve.org/CVERecord?id=CVE-2026-45872 Référence CVE CVE-2026-45873 https://www.cve.org/CVERecord?id=CVE-2026-45873 Référence CVE CVE-2026-45875 https://www.cve.org/CVERecord?id=CVE-2026-45875 Référence CVE CVE-2026-45877 https://www.cve.org/CVERecord?id=CVE-2026-45877 Référence CVE CVE-2026-45878 https://www.cve.org/CVERecord?id=CVE-2026-45878 Référence CVE CVE-2026-45879 https://www.cve.org/CVERecord?id=CVE-2026-45879 Référence CVE CVE-2026-45880 https://www.cve.org/CVERecord?id=CVE-2026-45880 Référence CVE CVE-2026-45881 https://www.cve.org/CVERecord?id=CVE-2026-45881 Référence CVE CVE-2026-45882 https://www.cve.org/CVERecord?id=CVE-2026-45882 Référence CVE CVE-2026-45883 https://www.cve.org/CVERecord?id=CVE-2026-45883 Référence CVE CVE-2026-45884 https://www.cve.org/CVERecord?id=CVE-2026-45884 Référence CVE CVE-2026-45885 https://www.cve.org/CVERecord?id=CVE-2026-45885 Référence CVE CVE-2026-45886 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-45848 https://www.cve.org/CVERecord?id=CVE-2026-45848 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-45856 https://www.cve.org/CVERecord?id=CVE-2026-45856 Référence CVE CVE-2026-45862 https://www.cve.org/CVERecord?id=CVE-2026-45862 Référence CVE CVE-2026-45870 https://www.cve.org/CVERecord?id=CVE-2026-45870 Référence CVE CVE-2026-45878 https://www.cve.org/CVERecord?id=CVE-2026-45878 Référence CVE CVE-2026-45886 https://www.cve.org/CVERecord?id=CVE-2026-45886 Référence CVE CVE-2026-45891 https://www.cve.org/CVERecord?id=CVE-2026-45891 Référence CVE CVE-2026-45894 https://www.cve.org/CVERecord?id=CVE-2026-45894 Référence CVE CVE-2026-45910 https://www.cve.org/CVERecord?id=CVE-2026-45910 Référence CVE CVE-2026-45912 https://www.cve.org/CVERecord?id=CVE-2026-45912 Référence CVE CVE-2026-45932 https://www.cve.org/CVERecord?id=CVE-2026-45932 Référence CVE CVE-2026-45940 https://www.cve.org/CVERecord?id=CVE-2026-45940 Référence CVE CVE-2026-45948 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45867 Référence CVE CVE-2026-45868 https://www.cve.org/CVERecord?id=CVE-2026-45868 Référence CVE CVE-2026-45869 https://www.cve.org/CVERecord?id=CVE-2026-45869 Référence CVE CVE-2026-45870 https://www.cve.org/CVERecord?id=CVE-2026-45870 Référence CVE CVE-2026-45871 https://www.cve.org/CVERecord?id=CVE-2026-45871 Référence CVE CVE-2026-45872 https://www.cve.org/CVERecord?id=CVE-2026-45872 Référence CVE CVE-2026-45873 https://www.cve.org/CVERecord?id=CVE-2026-45873 Référence CVE CVE-2026-45875 https://www.cve.org/CVERecord?id=CVE-2026-45875 Référence CVE CVE-2026-45877 https://www.cve.org/CVERecord?id=CVE-2026-45877 Référence CVE CVE-2026-45878 https://www.cve.org/CVERecord?id=CVE-2026-45878 Référence CVE CVE-2026-45879 https://www.cve.org/CVERecord?id=CVE-2026-45879 Référence CVE CVE-2026-45880 https://www.cve.org/CVERecord?id=CVE-2026-45880 Référence CVE CVE-2026-45881 https://www.cve.org/CVERecord?id=CVE-2026-45881 Référence CVE CVE-2026-45882 https://www.cve.org/CVERecord?id=CVE-2026-45882 Référence CVE CVE-2026-45883 https://www.cve.org/CVERecord?id=CVE-2026-45883 Référence CVE CVE-2026-45884 https://www.cve.org/CVERecord?id=CVE-2026-45884 Référence CVE CVE-2026-45885 https://www.cve.org/CVERecord?id=CVE-2026-45885 Référence CVE CVE-2026-45886 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45840 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-45856 https://www.cve.org/CVERecord?id=CVE-2026-45856 Référence CVE CVE-2026-45862 https://www.cve.org/CVERecord?id=CVE-2026-45862 Référence CVE CVE-2026-45870 https://www.cve.org/CVERecord?id=CVE-2026-45870 Référence CVE CVE-2026-45878 https://www.cve.org/CVERecord?id=CVE-2026-45878 Référence CVE CVE-2026-45886 https://www.cve.org/CVERecord?id=CVE-2026-45886 Référence CVE CVE-2026-45894 https://www.cve.org/CVERecord?id=CVE-2026-45894 Référence CVE CVE-2026-45910 https://www.cve.org/CVERecord?id=CVE-2026-45910 Référence CVE CVE-2026-45932 https://www.cve.org/CVERecord?id=CVE-2026-45932 Référence CVE CVE-2026-45940 https://www.cve.org/CVERecord?id=CVE-2026-45940 Référence CVE CVE-2026-45961 https://www.cve.org/CVERecord?id=CVE-2026-45961 Référence CVE CVE-2026-45964 https://www.cve.org/CVERecord?id=CVE-2026-45964 Référence CVE CVE-2026-45965 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45867 Référence CVE CVE-2026-45868 https://www.cve.org/CVERecord?id=CVE-2026-45868 Référence CVE CVE-2026-45869 https://www.cve.org/CVERecord?id=CVE-2026-45869 Référence CVE CVE-2026-45870 https://www.cve.org/CVERecord?id=CVE-2026-45870 Référence CVE CVE-2026-45871 https://www.cve.org/CVERecord?id=CVE-2026-45871 Référence CVE CVE-2026-45872 https://www.cve.org/CVERecord?id=CVE-2026-45872 Référence CVE CVE-2026-45873 https://www.cve.org/CVERecord?id=CVE-2026-45873 Référence CVE CVE-2026-45875 https://www.cve.org/CVERecord?id=CVE-2026-45875 Référence CVE CVE-2026-45877 https://www.cve.org/CVERecord?id=CVE-2026-45877 Référence CVE CVE-2026-45878 https://www.cve.org/CVERecord?id=CVE-2026-45878 Référence CVE CVE-2026-45879 https://www.cve.org/CVERecord?id=CVE-2026-45879 Référence CVE CVE-2026-45880 https://www.cve.org/CVERecord?id=CVE-2026-45880 Référence CVE CVE-2026-45881 https://www.cve.org/CVERecord?id=CVE-2026-45881 Référence CVE CVE-2026-45882 https://www.cve.org/CVERecord?id=CVE-2026-45882 Référence CVE CVE-2026-45883 https://www.cve.org/CVERecord?id=CVE-2026-45883 Référence CVE CVE-2026-45884 https://www.cve.org/CVERecord?id=CVE-2026-45884 Référence CVE CVE-2026-45885 https://www.cve.org/CVERecord?id=CVE-2026-45885 Référence CVE CVE-2026-45886 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43483 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-43501 https://www.cve.org/CVERecord?id=CVE-2026-43501 Référence CVE CVE-2026-43503 https://www.cve.org/CVERecord?id=CVE-2026-43503 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-45856 https://www.cve.org/CVERecord?id=CVE-2026-45856 Référence CVE CVE-2026-45878 https://www.cve.org/CVERecord?id=CVE-2026-45878 Référence CVE CVE-2026-45886 https://www.cve.org/CVERecord?id=CVE-2026-45886 Référence CVE CVE-2026-45898 https://www.cve.org/CVERecord?id=CVE-2026-45898 Référence CVE CVE-2026-45910 https://www.cve.org/CVERecord?id=CVE-2026-45910 Référence CVE CVE-2026-45932 https://www.cve.org/CVERecord?id=CVE-2026-45932 Référence CVE CVE-2026-45970 https://www.cve.org/CVERecord?id=CVE-2026-45970 Référence CVE CVE-2026-45983 https://www.cve.org/CVERecord?id=CVE-2026-45983 Référence CVE CVE-2026-45984 https://www.cve.org/CVERecord?id=CVE-2026-45984 Référence CVE CVE-2026-46004 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-45447 Référence CVE CVE-2026-45835 https://www.cve.org/CVERecord?id=CVE-2026-45835 Référence CVE CVE-2026-45841 https://www.cve.org/CVERecord?id=CVE-2026-45841 Référence CVE CVE-2026-45842 https://www.cve.org/CVERecord?id=CVE-2026-45842 Référence CVE CVE-2026-45843 https://www.cve.org/CVERecord?id=CVE-2026-45843 Référence CVE CVE-2026-45846 https://www.cve.org/CVERecord?id=CVE-2026-45846 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-45856 https://www.cve.org/CVERecord?id=CVE-2026-45856 Référence CVE CVE-2026-45870 https://www.cve.org/CVERecord?id=CVE-2026-45870 Référence CVE CVE-2026-45878 https://www.cve.org/CVERecord?id=CVE-2026-45878 Référence CVE CVE-2026-45886 https://www.cve.org/CVERecord?id=CVE-2026-45886 Référence CVE CVE-2026-45898 https://www.cve.org/CVERecord?id=CVE-2026-45898 Référence CVE CVE-2026-45910 https://www.cve.org/CVERecord?id=CVE-2026-45910 Référence CVE CVE-2026-45932 https://www.cve.org/CVERecord?id=CVE-2026-45932 Référence CVE CVE-2026-45942 https://www.cve.org/CVERecord?id=CVE-2026-45942 Référence CVE CVE-2026-45970 https://www.cve.org/CVERecord?id=CVE-2026-45970 Référence CVE CVE-2026-45983 https://www.cve.org/CVERecord?id=CVE-2026-45983 Référence CVE CVE-2026-45984 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.
Patch available
Affected
kernel-rt as a component of Red Hat Enterprise Linux 9; kernel-rt-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-rt-devel as a component of Red Hat Enterprise Linux 9; kernel-rt-devel-matched as a component of Red Hat Enterprise Linux 9; kernel-rt-kvm as a component of Red Hat Enterprise Linux 9; kernel-rt-modules as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-core as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-extra as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-internal as a component of Red Hat Enterprise Linux 9; kernel-rt-modules-partner as a component of Red Hat Enterprise Linux 9; kernel-rt-selftests-internal as a component of Red Hat Enterprise Linux 9; kernel-rt.src as a component of Red Hat Enterprise Linux 9
Fixed
kernel-64k-debug-debuginfo-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debug-devel-matched-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-debuginfo-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-64k-devel-matched-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.49.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-debuginfo-0:6.12.0-211.49.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.49.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-0:6.12.0-211.49.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.49.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debug-devel-matched-0:6.12.0-211.49.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.49.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-0:6.12.0-211.49.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-aarch64-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-ppc64le-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-s390x-0:6.12.0-211.49.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-debuginfo-common-x86_64-0:6.12.0-211.49.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.49.1.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.49.1.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.49.1.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10); kernel-devel-0:6.12.0-211.49.1.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10); and 582 more
Action
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.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 27 May 2026 · Last source change 5 Aug 2026, 12:28 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-32344
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD enriched

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 →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

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-32344↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update 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-45878 · cve.blacktree.nl