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

posix-cpu-timers: Prevent UAF caused by non-leader exec() race

Linux · Linux

7.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 25 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 8 Sep 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.64% 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 25 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.

25 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.100-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.180-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinux-6.12Vendor fix publishedDebian records a fixed source-package version for this release.6.12.100-1~deb12u1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.1.5-1Debian Security Tracker ↗Source updated 5 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.

3 current
CVE-2026-64560 · CSAF 2.0 · revision 24 · interimSUSE Product Security TeamCVE-2026-64560
52 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 Live Patching 15 SP4
  • kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP4
  • kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP4
Summary
In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: Prevent UAF caused by non-leader exec() race Wongi and Jungwoo decoded and reported a non-leader exec() related race which can result in an UAF: sys_timer_delete() exec() posix_cpu_timer_del() // Observes old leader p = pid_task(pid, pid_type); de_thread() switch_leader(); release_task(old_leader) __exit_signal(old_leader) sighand = lock(old_leader, sighand); posix_cpu_timers*_exit(); sighand = lock_task_sighand(p) unhash_task(old_leader); sh = lock(p, sighand) old_leader->sighand = NULL; unlock(sighand); (p->sighand == NULL) unlock(sh) return NULL; // Returns without action if(!sighand) return 0; free_posix_timer(); This is "harmless" unless the deleted timer was armed and enqueued in p->signal because on exec() a TGID targeted timer is inherited. As sys_timer_delete() freed the underlying posix timer object run_posix_cpu_timers() or any timerqueue related add/delete operations on other timers will access the freed object's timerqueue node, which results in an UAF. There is a similar problem vs. posix_cpu_timer_set(). For regular posix timers it just transiently returns -ESRCH to user space, but for the use case in do_cpu_nanosleep() it's the same UAF just that the k_itimer is allocated on the stack. Also posix_cpu_timer_rearm() fails to rearm the timer, which means it stops to expire. While debating solutions Frederic pointed out another problem: posix_cpu_timer_del(tmr) __exit_signal(p) posix_cpu_timers*_exit(p); unhash_task(p); p->sighand = NULL; sh = lock_task_sighand(p) sighand = p->sighand; if (!sighand) return NULL; lock(sighand); if (!sh) WARN_ON_ONCE(timer_queued(tmr)); On weakly ordered architectures it is not guaranteed that posix_cpu_timer_del() will observe the stores in posix_cpu_timers*_exit() when p->sighand is observed as NULL, which means the WARN() can be a false positive. Solve these issues by: 1) Changing the store in __exit_signal() to smp_store_release(). 2) Adding a smp_acquire__after_ctrl_dep() into the !sighand path of lock_task_sighand(). 3) Creating a helper function for looking up the task and locking sighand which does not return when sighand == NULL. Instead it retries the task lookup and only if that fails it gives up. 4) Using that helper in the three affected functions. #1/#2 ensures that the reader side which observes sighand == NULL also observes all preceeding stores, i.e. the stores in posix_cpu_timers*_exit() and the ones in unhash_task(). #3 ensures that the above described non-leader exec() situation is handled gracefully. When the task lookup returns the old leader, but sighand == NULL then it retries. In the non-leader exec() case the subsequent task lookup will observe the new leader due to #1/#2. In normal exit() scenarios the subsequent lookup fails. When the task lookup fails, the function also checks whether the timer is still enqueued and issues a warning if that's the case. Unfortunately there is nothing which can be done about it, but as the task is already not longer visible the timer should not be accessed anymore. This check also requires memory ordering, which is not provided when the first lookup fails. To achieve that the check is preceeded by a smp_rmb() which pairs with the smp_wmb() in write_seqlock() in __exit_signal(). That ensures that the stores in posix_cpu_timers*_exit() are visible. The history of the non-leader exec() issue goes back to the early days of posix CPU timers, which stored a pointer to the group leader task in the timer. That obviously fails when a non-leader exec() switches the leader. commit e0a70217107e ("posix-cpu-timers: workaround to suppress the problems with mt exec") added a temporary workaround for that in 2010 which surv ---truncated---
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-64560 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: posix-cpu-timers: Prevent UAF caused by non-leader exec() race
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 CPU timer functionality. A race condition, which is a timing issue between different operations, can occur when a process attempts to delete a timer while another operation is still trying to access it. This can lead to a Use-After-Free (UAF) vulnerability, where the system tries to use memory that has already been released. Such a vulnerability could potentially be exploited by a local attacker to cause system instability or lead to a 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.
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

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

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: Prevent UAF caused by non-leader exec() race Wongi and Jungwoo decoded and reported a non-leader exec() related race which can result in an UAF: sys_timer_delete() exec() posix_cpu_timer_del() // Observes old leader p = pid_task(pid, pid_type); de_thread() switch_leader(); release_task(old_leader) __exit_signal(old_leader) sighand = lock(old_leader, sighand); posix_cpu_timers*_exit(); sighand = lock_task_sighand(p) unhash_task(old_leader); sh = lock(p, sighand) old_leader->sighand = NULL; unlock(sighand); (p->sighand == NULL) unlock(sh) return NULL; // Returns without action if(!sighand) return 0; free_posix_timer(); This is "harmless" unless the deleted timer was armed and enqueued in p->signal because on exec() a TGID targeted timer is inherited. As sys_timer_delete() freed the underlying posix timer object run_posix_cpu_timers() or any timerqueue related add/delete operations on other timers will access the freed object's timerqueue node, which results in an UAF. There is a similar problem vs. posix_cpu_timer_set(). For regular posix timers it just transiently returns -ESRCH to user space, but for the use case in do_cpu_nanosleep() it's the same UAF just that the k_itimer is allocated on the stack. Also posix_cpu_timer_rearm() fails to rearm the timer, which means it stops to expire. While debating solutions Frederic pointed out another problem: posix_cpu_timer_del(tmr) __exit_signal(p) posix_cpu_timers*_exit(p); unhash_task(p); p->sighand = NULL; sh = lock_task_sighand(p) sighand = p->sighand; if (!sighand) return NULL; lock(sighand); if (!sh) WARN_ON_ONCE(timer_queued(tmr)); On weakly ordered architectures it is not guaranteed that posix_cpu_timer_del() will observe the stores in posix_cpu_timers*_exit() when p->sighand is observed as NULL, which means the WARN() can be a false positive. Solve these issues by: 1) Changing the store in __exit_signal() to smp_store_release(). 2) Adding a smp_acquire__after_ctrl_dep() into the !sighand path of lock_task_sighand(). 3) Creating a helper function for looking up the task and locking sighand which does not return when sighand == NULL. Instead it retries the task lookup and only if that fails it gives up. 4) Using that helper in the three affected functions. #1/#2 ensures that the reader side which observes sighand == NULL also observes all preceeding stores, i.e. the stores in posix_cpu_timers*_exit() and the ones in unhash_task(). #3 ensures that the above described non-leader exec() situation is handled gracefully. When the task lookup returns the old leader, but sighand == NULL then it retries. In the non-leader exec() case the subsequent task lookup will observe the new leader due to #1/#2. In normal exit() scenarios the subsequent lookup fails. When the task lookup fails, the function also checks whether the timer is still enqueued and issues a warning if that's the case. Unfortunately there is nothing which can be done about it, but as the task is already not longer visible the timer should not be accessed anymore. This check also requires memory ordering, which is not provided when the first lookup fails. To achieve that the check is preceeded by a smp_rmb() which pairs with the smp_wmb() in write_seqlock() in __exit_signal(). That ensures that the stores in posix_cpu_timers*_exit() are visible. The history of the non-leader exec() issue goes back to the early days of posix CPU timers, which stored a pointer to the group leader task in the timer. That obviously fails when a non-leader exec() switches the leader. commit e0a70217107e ("posix-cpu-timers: workaround to suppress the problems with mt exec") added a temporary workaround for that in 2010 which surv ---truncated---
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
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-50417

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: Prevent UAF caused by non-leader exec() race Wongi and Jungwoo decoded and reported a non-leader exec() related race which can result in an UAF: sys_timer_delete() exec() posix_cpu_timer_del() // Observes old leader p = pid_task(pid, pid_type); de_thread() switch_leader(); release_task(old_leader) __exit_signal(old_leader) sighand = lock(old_leader, sighand); posix_cpu_timers*_exit(); sighand = lock_task_sighand(p) unhash_task(old_leader); sh = lock(p, sighand) old_leader->sighand = NULL; unlock(sighand); (p->sighand == NULL) unlock(sh) return NULL; // Returns without action if(!sighand) return 0; free_posix_timer(); This is "harmless" unless the deleted timer was armed and enqueued in p->signal because on exec() a TGID targeted timer is inherited. As sys_timer_delete() freed the underlying posix timer object run_posix_cpu_timers() or any timerqueue related add/delete operations on other timers will access the freed object's timerqueue node, which results in an UAF. There is a similar problem vs. posix_cpu_timer_set(). For regular posix timers it just transiently returns -ESRCH to user space, but for the use case in do_cpu_nanosleep() it's the same UAF just that the k_itimer is allocated on the stack. Also posix_cpu_timer_rearm() fails to rearm the timer, which means it stops to expire. While debating solutions Frederic pointed out another problem: posix_cpu_timer_del(tmr) __exit_signal(p) posix_cpu_timers*_exit(p); unhash_task(p); p->sighand = NULL; sh = lock_task_sighand(p) sighand = p->sighand; if (!sighand) return NULL; lock(sighand); if (!sh) WARN_ON_ONCE(timer_queued(tmr)); On weakly ordered architectures it is not guaranteed that posix_cpu_timer_del() will observe the stores in posix_cpu_timers*_exit() when p->sighand is observed as NULL, which means the WARN() can be a false positive. Solve these issues by: 1) Changing the store in __exit_signal() to smp_store_release(). 2) Adding a smp_acquire__after_ctrl_dep() into the !sighand path of lock_task_sighand(). 3) Creating a helper function for looking up the task and locking sighand which does not return when sighand == NULL. Instead it retries the task lookup and only if that fails it gives up. 4) Using that helper in the three affected functions. #1/#2 ensures that the reader side which observes sighand == NULL also observes all preceeding stores, i.e. the stores in posix_cpu_timers*_exit() and the ones in unhash_task(). #3 ensures that the above described non-leader exec() situation is handled gracefully. When the task lookup returns the old leader, but sighand == NULL then it retries. In the non-leader exec() case the subsequent task lookup will observe the new leader due to #1/#2. In normal exit() scenarios the subsequent lookup fails. When the task lookup fails, the function also checks whether the timer is still enqueued and issues a warning if that's the case. Unfortunately there is nothing which can be done about it, but as the task is already not longer visible the timer should not be accessed anymore. This check also requires memory ordering, which is not provided when the first lookup fails. To achieve that the check is preceeded by a smp_rmb() which pairs with the smp_wmb() in write_seqlock() in __exit_signal(). That ensures that the stores in posix_cpu_timers*_exit() are visible. The history of the non-leader exec() issue goes back to the early days of posix CPU timers, which stored a pointer to the group leader task in the timer. That obviously fails when a non-leader exec() switches the leader. commit e0a70217107e ("posix-cpu-timers: workaround to suppress the problems with mt exec") added a temporary workaround for that in 2010 which surv ---truncated---

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
7.8 · CVSS 3.1
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 25 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: posix-cpu-timers: Prevent UAF caused by non-leader exec() race Wongi and Jungwoo decoded and reported a non-leader exec() related race which can result in an UAF: sys_timer_delete() exec() posix_cpu_timer_del() // Observes old leader p = pid_task(pid, pid_type); de_thread() switch_leader(); release_task(old_leader) __exit_signal(old_leader) sighand = lock(old_leader, sighand); posix_cpu_timers*_exit(); sighand = lock_task_sighand(p) unhash_task(old_leader); sh = lock(p, sighand) old_leader->sighand = NULL; unlock(sighand); (p->sighand == NULL) unlock(sh) return NULL; // Returns without action if(!sighand) return 0; free_posix_timer(); This is "harmless" unless the deleted timer was armed and enqueued in p->signal because on exec() a TGID targeted timer is inherited. As sys_timer_delete() freed the underlying posix timer object run_posix_cpu_timers() or any timerqueue related add/delete operations on other timers will access the freed object's timerqueue node, which results in an UAF. There is a similar problem vs. posix_cpu_timer_set(). For regular posix timers it just transiently returns -ESRCH to user space, but for the use case in do_cpu_nanosleep() it's the same UAF just that the k_itimer is allocated on the stack. Also posix_cpu_timer_rearm() fails to rearm the timer, which means it stops to expire. While debating solutions Frederic pointed out another problem: posix_cpu_timer_del(tmr) __exit_signal(p) posix_cpu_timers*_exit(p); unhash_task(p); p->sighand = NULL; sh = lock_task_sighand(p) sighand = p->sighand; if (!sighand) return NULL; lock(sighand); if (!sh) WARN_ON_ONCE(timer_queued(tmr)); On weakly ordered architectures it is not guaranteed that posix_cpu_timer_del() will observe the stores in posix_cpu_timers*_exit() when p->sighand is observed as NULL, which means the WARN() can be a false positive. Solve these issues by: 1) Changing the store in __exit_signal() to smp_store_release(). 2) Adding a smp_acquire__after_ctrl_dep() into the !sighand path of lock_task_sighand(). 3) Creating a helper function for looking up the task and locking sighand which does not return when sighand == NULL. Instead it retries the task lookup and only if that fails it gives up. 4) Using that helper in the three affected functions. #1/#2 ensures that the reader side which observes sighand == NULL also observes all preceeding stores, i.e. the stores in posix_cpu_timers*_exit() and the ones in unhash_task(). #3 ensures that the above described non-leader exec() situation is handled gracefully. When the task lookup returns the old leader, but sighand == NULL then it retries. In the non-leader exec() case the subsequent task lookup will observe the new leader due to #1/#2. In normal exit() scenarios the subsequent lookup fails. When the task lookup fails, the function also checks whether the timer is still enqueued and issues a warning if that's the case. Unfortunately there is nothing which can be done about it, but as the task is already not longer visible the timer should not be accessed anymore. This check also requires memory ordering, which is not provided when the first lookup fails. To achieve that the check is preceeded by a smp_rmb() which pairs with the smp_wmb() in write_seqlock() in __exit_signal(). That ensures that the stores in posix_cpu_timers*_exit() are visible. The history of the non-leader exec() issue goes back to the early days of posix CPU timers, which stored a pointer to the group leader task in the timer. That obviously fails when a non-leader exec() switches the leader. commit e0a70217107e ("posix-cpu-timers: workaround to suppress the problems with mt exec") added a temporary workaround for that in 2010 which surv ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: Prevent UAF caused by non-leader exec() race Wongi and Jungwoo decoded and reported a non-leader exec() related race which can result in an UAF: sys_timer_delete() exec() posix_cpu_timer_del() // Observes old leader p = pid_task(pid, pid_type); de_thread() switch_leader(); release_task(old_leader) __exit_signal(old_leader) sighand = lock(old_leader, sighand); posix_cpu_timers*_exit(); sighand = lock_task_sighand(p) unhash_task(old_leader); sh = lock(p, sighand) old_leader->sighand = NULL; unlock(sighand); (p->sighand == NULL) unlock(sh) return NULL; // Returns without action if(!sighand) return 0; free_posix_timer(); This is "harmless" unless the deleted timer was armed and enqueued in p->signal because on exec() a TGID targeted timer is inherited. As sys_timer_delete() freed the underlying posix timer object run_posix_cpu_timers() or any timerqueue related add/delete operations on other timers will access the freed object's timerqueue node, which results in an UAF. There is a similar problem vs. posix_cpu_timer_set(). For regular posix timers it just transiently returns -ESRCH to user space, but for the use case in do_cpu_nanosleep() it's the same UAF just that the k_itimer is allocated on the stack. Also posix_cpu_timer_rearm() fails to rearm the timer, which means it stops to expire. While debating solutions Frederic pointed out another problem: posix_cpu_timer_del(tmr) __exit_signal(p) posix_cpu_timers*_exit(p); unhash_task(p); p->sighand = NULL; sh = lock_task_sighand(p) sighand = p->sighand; if (!sighand) return NULL; lock(sighand); if (!sh) WARN_ON_ONCE(timer_queued(tmr)); On weakly ordered architectures it is not guaranteed that posix_cpu_timer_del() will observe the stores in posix_cpu_timers*_exit() when p->sighand is observed as NULL, which means the WARN() can be a false positive. Solve these issues by: 1) Changing the store in __exit_signal() to smp_store_release(). 2) Adding a smp_acquire__after_ctrl_dep() into the !sighand path of lock_task_sighand(). 3) Creating a helper function for looking up the task and locking sighand which does not return when sighand == NULL. Instead it retries the task lookup and only if that fails it gives up. 4) Using that helper in the three affected functions. #1/#2 ensures that the reader side which observes sighand == NULL also observes all preceeding stores, i.e. the stores in posix_cpu_timers*_exit() and the ones in unhash_task(). #3 ensures that the above described non-leader exec() situation is handled gracefully. When the task lookup returns the old leader, but sighand == NULL then it retries. In the non-leader exec() case the subsequent task lookup will observe the new leader due to #1/#2. In normal exit() scenarios the subsequent lookup fails. When the task lookup fails, the function also checks whether the timer is still enqueued and issues a warning if that's the case. Unfortunately there is nothing which can be done about it, but as the task is already not longer visible the timer should not be accessed anymore. This check also requires memory ordering, which is not provided when the first lookup fails. To achieve that the check is preceeded by a smp_rmb() which pairs with the smp_wmb() in write_seqlock() in __exit_signal(). That ensures that the stores in posix_cpu_timers*_exit() are visible. The history of the non-leader exec() issue goes back to the early days of posix CPU timers, which stored a pointer to the group leader task in the timer. That obviously fails when a non-leader exec() switches the leader. commit e0a70217107e ("posix-cpu-timers: workaround to suppress the problems with mt exec") added a temporary workaround for that in 2010 which surv ---truncated---

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: posix-cpu-timers: Prevent UAF caused by non-leader exec() race Wongi and Jungwoo decoded and reported a non-leader exec() related race which can result in an UAF: sys_timer_delete() exec() posix_cpu_timer_del() // Observes old leader p = pid_task(pid, pid_type); de_thread() switch_leader(); release_task(old_leader) __exit_signal(old_leader) sighand = lock(old_leader, sighand); posix_cpu_timers*_exit(); sighand = lock_task_sighand(p) unhash_task(old_leader); sh = lock(p, sighand) old_leader->sighand = NULL; unlock(sighand); (p->sighand == NULL) unlock(sh) return NULL; // Returns without action if(!sighand) return 0; free_posix_timer(); This is "harmless" unless the deleted timer was armed and enqueued in p->signal because on exec() a TGID targeted timer is inherited. As sys_timer_delete() freed the underlying posix timer object run_posix_cpu_timers() or any timerqueue related add/delete operations on other timers will access the freed object's timerqueue node, which results in an UAF. There is a similar problem vs. posix_cpu_timer_set(). For regular posix timers it just transiently returns -ESRCH to user space, but for the use case in do_cpu_nanosleep() it's the same UAF just that the k_itimer is allocated on the stack. Also posix_cpu_timer_rearm() fails to rearm the timer, which means it stops to expire. While debating solutions Frederic pointed out another problem: posix_cpu_timer_del(tmr) __exit_signal(p) posix_cpu_timers*_exit(p); unhash_task(p); p->sighand = NULL; sh = lock_task_sighand(p) sighand = p->sighand; if (!sighand) return NULL; lock(sighand); if (!sh) WARN_ON_ONCE(timer_queued(tmr)); On weakly ordered architectures it is not guaranteed that posix_cpu_timer_del() will observe the stores in posix_cpu_timers*_exit() when p->sighand is observed as NULL, which means the WARN() can be a false positive. Solve these issues by: 1) Changing the store in __exit_signal() to smp_store_release(). 2) Adding a smp_acquire__after_ctrl_dep() into the !sighand path of lock_task_sighand(). 3) Creating a helper function for looking up the task and locking sighand which does not return when sighand == NULL. Instead it retries the task lookup and only if that fails it gives up. 4) Using that helper in the three affected functions. #1/#2 ensures that the reader side which observes sighand == NULL also observes all preceeding stores, i.e. the stores in posix_cpu_timers*_exit() and the ones in unhash_task(). #3 ensures that the above described non-leader exec() situation is handled gracefully. When the task lookup returns the old leader, but sighand == NULL then it retries. In the non-leader exec() case the subsequent task lookup will observe the new leader due to #1/#2. In normal exit() scenarios the subsequent lookup fails. When the task lookup fails, the function also checks whether the timer is still enqueued and issues a warning if that's the case. Unfortunately there is nothing which can be done about it, but as the task is already not longer visible the timer should not be accessed anymore. This check also requires memory ordering, which is not provided when the first lookup fails. To achieve that the check is preceeded by a smp_rmb() which pairs with the smp_wmb() in write_seqlock() in __exit_signal(). That ensures that the stores in posix_cpu_timers*_exit() are visible. The history of the non-leader exec() issue goes back to the early days of posix CPU timers, which stored a pointer to the group leader task in the timer. That obviously fails when a non-leader exec() switches the leader. commit e0a70217107e ("posix-cpu-timers: workaround to suppress the problems with mt exec") added a temporary workaround for that in 2010 which surv ---truncated---

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.

ENISA EUVD · EUVD-2026-50417Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: posix-cpu-timers: Prevent UAF caused by non-leader exec() race Wongi and Jungwoo decoded and reported a non-leader exec() related race which can result in an UAF: sys_timer_delete() exec() posix_cpu_timer_del() // Observes old leader p = pid_task(pid, pid_type); de_thread() switch_leader(); release_task(old_leader) __exit_signal(old_leader) sighand = lock(old_leader, sighand); posix_cpu_timers*_exit(); sighand = lock_task_sighand(p) unhash_task(old_leader); sh = lock(p, sighand) old_leader->sighand = NULL; unlock(sighand); (p->sighand == NULL) unlock(sh) return NULL; // Returns without action if(!sighand) return 0; free_posix_timer(); This is "harmless" unless the deleted timer was armed and enqueued in p->signal because on exec() a TGID targeted timer is inherited. As sys_timer_delete() freed the underlying posix timer object run_posix_cpu_timers() or any timerqueue related add/delete operations on other timers will access the freed object's timerqueue node, which results in an UAF. There is a similar problem vs. posix_cpu_timer_set(). For regular posix timers it just transiently returns -ESRCH to user space, but for the use case in do_cpu_nanosleep() it's the same UAF just that the k_itimer is allocated on the stack. Also posix_cpu_timer_rearm() fails to rearm the timer, which means it stops to expire. While debating solutions Frederic pointed out another problem: posix_cpu_timer_del(tmr) __exit_signal(p) posix_cpu_timers*_exit(p); unhash_task(p); p->sighand = NULL; sh = lock_task_sighand(p) sighand = p->sighand; if (!sighand) return NULL; lock(sighand); if (!sh) WARN_ON_ONCE(timer_queued(tmr)); On weakly ordered architectures it is not guaranteed that posix_cpu_timer_del() will observe the stores in posix_cpu_timers*_exit() when p->sighand is observed as NULL, which means the WARN() can be a false positive. Solve these issues by: 1) Changing the store in __exit_signal() to smp_store_release(). 2) Adding a smp_acquire__after_ctrl_dep() into the !sighand path of lock_task_sighand(). 3) Creating a helper function for looking up the task and locking sighand which does not return when sighand == NULL. Instead it retries the task lookup and only if that fails it gives up. 4) Using that helper in the three affected functions. #1/#2 ensures that the reader side which observes sighand == NULL also observes all preceeding stores, i.e. the stores in posix_cpu_timers*_exit() and the ones in unhash_task(). #3 ensures that the above described non-leader exec() situation is handled gracefully. When the task lookup returns the old leader, but sighand == NULL then it retries. In the non-leader exec() case the subsequent task lookup will observe the new leader due to #1/#2. In normal exit() scenarios the subsequent lookup fails. When the task lookup fails, the function also checks whether the timer is still enqueued and issues a warning if that's the case. Unfortunately there is nothing which can be done about it, but as the task is already not longer visible the timer should not be accessed anymore. This check also requires memory ordering, which is not provided when the first lookup fails. To achieve that the check is preceeded by a smp_rmb() which pairs with the smp_wmb() in write_seqlock() in __exit_signal(). That ensures that the stores in posix_cpu_timers*_exit() are visible. The history of the non-leader exec() issue goes back to the early days of posix CPU timers, which stored a pointer to the group leader task in the timer. That obviously fails when a non-leader exec() switches the leader. commit e0a70217107e ("posix-cpu-timers: workaround to suppress the problems with mt exec") added a temporary workaround for that in 2010 which surv ---truncated---

Official EUVD record ↗
BSI · German · WID-SEC-2026-3623IBM DataPower Gateway: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um beliebigen Programmcode auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen, einen Denial-of-Service-Zustand auszulösen oder Cross-Site-Scripting-Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-2591Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260805Security Bulletin 5 Aug 2026

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

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

d?id=CVE-2026-64234 Référence CVE CVE-2026-64242 https://www.cve.org/CVERecord?id=CVE-2026-64242 Référence CVE CVE-2026-64298 https://www.cve.org/CVERecord?id=CVE-2026-64298 Référence CVE CVE-2026-64330 https://www.cve.org/CVERecord?id=CVE-2026-64330 Référence CVE CVE-2026-64336 https://www.cve.org/CVERecord?id=CVE-2026-64336 Référence CVE CVE-2026-64345 https://www.cve.org/CVERecord?id=CVE-2026-64345 Référence CVE CVE-2026-64347 https://www.cve.org/CVERecord?id=CVE-2026-64347 Référence CVE CVE-2026-64465 https://www.cve.org/CVERecord?id=CVE-2026-64465 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-64560 https://www.cve.org/CVERecord?id=CVE-2026-64560 Référence CVE CVE-2026-64561 https://www.cve.org/CVERecord?id=CVE-2026-64561 Référence CVE CVE-2026-64564 https://www.cve.org/CVERecord?id=CVE-2026-64564 Référence CVE CVE-2026-64600 https://www.cve.org/CVERecord?id=CVE-2026-64600 Gestion détaillée du document le 28 août 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des sy

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

d?id=CVE-2026-64242 Référence CVE CVE-2026-64330 https://www.cve.org/CVERecord?id=CVE-2026-64330 Référence CVE CVE-2026-64336 https://www.cve.org/CVERecord?id=CVE-2026-64336 Référence CVE CVE-2026-64345 https://www.cve.org/CVERecord?id=CVE-2026-64345 Référence CVE CVE-2026-64347 https://www.cve.org/CVERecord?id=CVE-2026-64347 Référence CVE CVE-2026-64357 https://www.cve.org/CVERecord?id=CVE-2026-64357 Référence CVE CVE-2026-64465 https://www.cve.org/CVERecord?id=CVE-2026-64465 Référence CVE CVE-2026-64528 https://www.cve.org/CVERecord?id=CVE-2026-64528 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-64560 https://www.cve.org/CVERecord?id=CVE-2026-64560 Référence CVE CVE-2026-64561 https://www.cve.org/CVERecord?id=CVE-2026-64561 Référence CVE CVE-2026-64564 https://www.cve.org/CVERecord?id=CVE-2026-64564 Référence CVE CVE-2026-64600 https://www.cve.org/CVERecord?id=CVE-2026-64600 Gestion détaillée du document le 21 août 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des sy

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

d?id=CVE-2026-64551 Référence CVE CVE-2026-64552 https://www.cve.org/CVERecord?id=CVE-2026-64552 Référence CVE CVE-2026-64553 https://www.cve.org/CVERecord?id=CVE-2026-64553 Référence CVE CVE-2026-64554 https://www.cve.org/CVERecord?id=CVE-2026-64554 Référence CVE CVE-2026-64555 https://www.cve.org/CVERecord?id=CVE-2026-64555 Référence CVE CVE-2026-64556 https://www.cve.org/CVERecord?id=CVE-2026-64556 Référence CVE CVE-2026-64557 https://www.cve.org/CVERecord?id=CVE-2026-64557 Référence CVE CVE-2026-64558 https://www.cve.org/CVERecord?id=CVE-2026-64558 Référence CVE CVE-2026-64559 https://www.cve.org/CVERecord?id=CVE-2026-64559 Référence CVE CVE-2026-64560 https://www.cve.org/CVERecord?id=CVE-2026-64560 Référence CVE CVE-2026-64582 https://www.cve.org/CVERecord?id=CVE-2026-64582 Référence CVE CVE-2026-64585 https://www.cve.org/CVERecord?id=CVE-2026-64585 Référence CVE CVE-2026-64589 https://www.cve.org/CVERecord?id=CVE-2026-64589 Référence CVE CVE-2026-64590 https://www.cve.org/CVERecord?id=CVE-2026-64590 Référence CVE CVE-2026-64592 https://www.cve.org/CVERecord?id=CVE-2026-64592 Référence CVE CVE-2026-64593 https://www.cve.org/CVERecord?id=CVE-2026-64593 Référence CVE CVE-2026-64594 https://www.cve.org/CVERecord?id=CVE-2026-64594 Référence CVE CVE-2026-64597 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-63975 Référence CVE CVE-2026-63984 https://www.cve.org/CVERecord?id=CVE-2026-63984 Référence CVE CVE-2026-63994 https://www.cve.org/CVERecord?id=CVE-2026-63994 Référence CVE CVE-2026-64106 https://www.cve.org/CVERecord?id=CVE-2026-64106 Référence CVE CVE-2026-64189 https://www.cve.org/CVERecord?id=CVE-2026-64189 Référence CVE CVE-2026-64298 https://www.cve.org/CVERecord?id=CVE-2026-64298 Référence CVE CVE-2026-64330 https://www.cve.org/CVERecord?id=CVE-2026-64330 Référence CVE CVE-2026-64465 https://www.cve.org/CVERecord?id=CVE-2026-64465 Référence CVE CVE-2026-64530 https://www.cve.org/CVERecord?id=CVE-2026-64530 Référence CVE CVE-2026-64560 https://www.cve.org/CVERecord?id=CVE-2026-64560 Référence CVE CVE-2026-64561 https://www.cve.org/CVERecord?id=CVE-2026-64561 Référence CVE CVE-2026-64564 https://www.cve.org/CVERecord?id=CVE-2026-64564 Référence CVE CVE-2026-64600 https://www.cve.org/CVERecord?id=CVE-2026-64600 Gestion détaillée du document le 14 août 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des sy

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

d?id=CVE-2026-64547 Référence CVE CVE-2026-64548 https://www.cve.org/CVERecord?id=CVE-2026-64548 Référence CVE CVE-2026-64549 https://www.cve.org/CVERecord?id=CVE-2026-64549 Référence CVE CVE-2026-64550 https://www.cve.org/CVERecord?id=CVE-2026-64550 Référence CVE CVE-2026-64551 https://www.cve.org/CVERecord?id=CVE-2026-64551 Référence CVE CVE-2026-64552 https://www.cve.org/CVERecord?id=CVE-2026-64552 Référence CVE CVE-2026-64553 https://www.cve.org/CVERecord?id=CVE-2026-64553 Référence CVE CVE-2026-64554 https://www.cve.org/CVERecord?id=CVE-2026-64554 Référence CVE CVE-2026-64557 https://www.cve.org/CVERecord?id=CVE-2026-64557 Référence CVE CVE-2026-64560 https://www.cve.org/CVERecord?id=CVE-2026-64560 Référence CVE CVE-2026-64600 https://www.cve.org/CVERecord?id=CVE-2026-64600 Gestion détaillée du document le 07 août 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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

d?id=CVE-2026-64550 Référence CVE CVE-2026-64551 https://www.cve.org/CVERecord?id=CVE-2026-64551 Référence CVE CVE-2026-64552 https://www.cve.org/CVERecord?id=CVE-2026-64552 Référence CVE CVE-2026-64553 https://www.cve.org/CVERecord?id=CVE-2026-64553 Référence CVE CVE-2026-64554 https://www.cve.org/CVERecord?id=CVE-2026-64554 Référence CVE CVE-2026-64555 https://www.cve.org/CVERecord?id=CVE-2026-64555 Référence CVE CVE-2026-64557 https://www.cve.org/CVERecord?id=CVE-2026-64557 Référence CVE CVE-2026-64558 https://www.cve.org/CVERecord?id=CVE-2026-64558 Référence CVE CVE-2026-64559 https://www.cve.org/CVERecord?id=CVE-2026-64559 Référence CVE CVE-2026-64560 https://www.cve.org/CVERecord?id=CVE-2026-64560 Gestion détaillée du document le 07 août 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

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
Linux: < 5.7, 5.10.262 ≤ 5.10.*, 5.15.213 ≤ 5.15.*, 6.1.180 ≤ 6.1.*, 6.6.147 ≤ 6.6.*, 6.12.100 ≤ 6.12.*, 6.18.41 ≤ 6.18.*, 7.1.5 ≤ 7.1.*, 7.2 ≤ *
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 29 Jul 2026 · Last source change 8 Sept 2026, 08:50 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-50417
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD received

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. Affected versionsThe structured affected or fixed version information changed.
    Before
    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 Live Patching 15 SP4; kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP4; kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP4; kernel-source as component of SUSE Linux Enterprise Live Patching 15 SP4; kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP5; kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP5; kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP5; kernel-source as component of SUSE Linux Enterprise Live Patching 15 SP5; kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP7; kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP7; kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP7; kernel-source as component of SUSE Linux Enterprise Live Patching 15 SP7; kernel-default as component of SUSE Linux Enterprise Module for Legacy 15 SP7; kernel-source as component of SUSE Linux Enterprise Module for Legacy 15 SP7; reiserfs-kmp-default as component of SUSE Linux Enterprise Module for Legacy 15 SP7; kernel-default as component of SUSE Linux Enterprise Server 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Server 15 SP7; kernel-source as component of SUSE Linux Enterprise Server 15 SP7; reiserfs-kmp-default as component of SUSE Linux Enterprise Server 15 SP7; kernel-default as component of SUSE Linux Enterprise Server for SAP Applications 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Server for SAP Applications 15 SP7; and 20 more · Fixed: kernel-obs-build-6.12.0-160000.37.1 as component of SUSE Linux Micro Extras 6.2; kernel-syms-6.12.0-160000.37.1 as component of SUSE Linux Micro Extras 6.2
    After
    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 Live Patching 15 SP4; kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP4; kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP4; kernel-source as component of SUSE Linux Enterprise Live Patching 15 SP4; kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP5; kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP5; kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP5; kernel-source as component of SUSE Linux Enterprise Live Patching 15 SP5; kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP7; kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP7; kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP7; kernel-source as component of SUSE Linux Enterprise Live Patching 15 SP7; kernel-default as component of SUSE Linux Enterprise Module for Legacy 15 SP7; kernel-source as component of SUSE Linux Enterprise Module for Legacy 15 SP7; reiserfs-kmp-default as component of SUSE Linux Enterprise Module for Legacy 15 SP7; kernel-default as component of SUSE Linux Enterprise Server 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Server 15 SP7; kernel-source as component of SUSE Linux Enterprise Server 15 SP7; reiserfs-kmp-default as component of SUSE Linux Enterprise Server 15 SP7; kernel-default as component of SUSE Linux Enterprise Server for SAP Applications 15 SP7; kernel-default-extra as component of SUSE Linux Enterprise Server for SAP Applications 15 SP7; and 22 more
    SUSE Product Security Team ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    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
    After
    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 887 more
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 < 67aa823e3e8c229c6d374df79c804f6721cb83b6; 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 < d8bcb28abad857f1415da7656f19b2ada90af04f; 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 < cc35ddbc497311e0b6b9a6a6a4f4d1217d6ab1aa; 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 < 12a891c773aeb5823d63dbd0cb2ab931d6c21c9b; 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 < e74443f5db0037c556ef436fa64b88bf4ea08f83; 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 < 6a7ecc25abe6f0fecc6e62a05096987200edbd02; 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 < ad1cafa1bdaa71da85d71cac053838bbe97852b6; 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 < 920f893f735e92ba3a1cd9256899a186b161928d · Fixed: < 5.7; 5.10.262 ≤ 5.10.*; 5.15.213 ≤ 5.15.*; 6.1.180 ≤ 6.1.*; 6.6.147 ≤ 6.6.*; 6.12.100 ≤ 6.12.*; 6.18.41 ≤ 6.18.*; 7.1.5 ≤ 7.1.*
    After
    Linux: 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 < 67aa823e3e8c229c6d374df79c804f6721cb83b6, 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 < d8bcb28abad857f1415da7656f19b2ada90af04f, 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 < cc35ddbc497311e0b6b9a6a6a4f4d1217d6ab1aa, 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 < 12a891c773aeb5823d63dbd0cb2ab931d6c21c9b, 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 < e74443f5db0037c556ef436fa64b88bf4ea08f83, 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 < 6a7ecc25abe6f0fecc6e62a05096987200edbd02, 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 < ad1cafa1bdaa71da85d71cac053838bbe97852b6, 55e8c8eb2c7b6bf30e99423ccfe7ca032f498f59 < 920f893f735e92ba3a1cd9256899a186b161928d, 5.7 · Fixed: Linux: < 5.7, 5.10.262 ≤ 5.10.*, 5.15.213 ≤ 5.15.*, 6.1.180 ≤ 6.1.*, 6.6.147 ≤ 6.6.*, 6.12.100 ≤ 6.12.*, 6.18.41 ≤ 6.18.*, 7.1.5 ≤ 7.1.*, 7.2 ≤ *
    CNA ↗
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-50417↗Vendor CSAF · SUSE Product Security Team↗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-64560 · cve.blacktree.nl