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

irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT

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 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

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

Evidence used

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

Compensating controls

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

Verification

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

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

Cross-source reconciliation

Remediation availability differs by product scope

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

Distribution package intelligence

Release-specific package status

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

24 package states
Package result overrides the generic status

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

Repository candidate not checked

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

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

Authoritative vendor CSAF and VEX advisories

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

1 current
CVE-2026-64073 · CSAF 2.0 · revision 11 · interimSUSE Product Security TeamCVE-2026-64073
209 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.1
Summary
In the Linux kernel, the following vulnerability has been resolved: irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT On PREEMPT_RT, non-HARD irq_work runs in per-CPU kthreads via run_irq_workd(), so irq_work_sync() uses rcuwait() to wait for BUSY==0. After irq_work_single() clears BUSY via atomic_cmpxchg(), it still dereferences @work for irq_work_is_hard() and rcuwait_wake_up(). An irq_work_sync() caller on another CPU that enters after BUSY is cleared can observe BUSY==0 immediately, return, and free the work before those accesses complete - causing a use-after-free. Fix this by wrapping run_irq_workd() in guard(rcu)() so that the entire irq_work_single() execution is within an RCU read-side critical section. Then add synchronize_rcu() in irq_work_sync() after rcuwait_wait_event() to ensure the caller waits for the RCU grace period before returning, preventing premature frees.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

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

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

Official European source

ENISA European Vulnerability Database

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

1 current
ENISA EUVD identifier

EUVD-2026-45646

No EUVD known-exploited evidence

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

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

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT On PREEMPT_RT, non-HARD irq_work runs in per-CPU kthreads via run_irq_workd(), so irq_work_sync() uses rcuwait() to wait for BUSY==0. After irq_work_single() clears BUSY via atomic_cmpxchg(), it still dereferences @work for irq_work_is_hard() and rcuwait_wake_up(). An irq_work_sync() caller on another CPU that enters after BUSY is cleared can observe BUSY==0 immediately, return, and free the work before those accesses complete — causing a use-after-free. Fix this by wrapping run_irq_workd() in guard(rcu)() so that the entire irq_work_single() execution is within an RCU read-side critical section. Then add synchronize_rcu() in irq_work_sync() after rcuwait_wait_event() to ensure the caller waits for the RCU grace period before returning, preventing premature frees.

What

In the Linux kernel, the following vulnerability has been resolved: irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT On PREEMPT_RT, non-HARD irq_work runs in per-CPU kthreads via run_irq_workd(), so irq_work_sync() uses rcuwait() to wait for BUSY==0. After irq_work_single() clears BUSY via atomic_cmpxchg(), it still dereferences @work for irq_work_is_hard() and rcuwait_wake_up(). An irq_work_sync() caller on another CPU that enters after BUSY is cleared can observe BUSY==0 immediately, return, and free the work before those accesses complete — causing a use-after-free. Fix this by wrapping run_irq_workd() in guard(rcu)() so that the entire irq_work_single() execution is within an RCU read-side critical section. Then add synchronize_rcu() in irq_work_sync() after rcuwait_wait_event() to ensure the caller waits for the RCU grace period before returning, preventing premature frees.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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: irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT On PREEMPT_RT, non-HARD irq_work runs in per-CPU kthreads via run_irq_workd(), so irq_work_sync() uses rcuwait() to wait for BUSY==0. After irq_work_single() clears BUSY via atomic_cmpxchg(), it still dereferences @work for irq_work_is_hard() and rcuwait_wake_up(). An irq_work_sync() caller on another CPU that enters after BUSY is cleared can observe BUSY==0 immediately, return, and free the work before those accesses complete — causing a use-after-free. Fix this by wrapping run_irq_workd() in guard(rcu)() so that the entire irq_work_single() execution is within an RCU read-side critical section. Then add synchronize_rcu() in irq_work_sync() after rcuwait_wait_event() to ensure the caller waits for the RCU grace period before returning, preventing premature frees.

Why

The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.

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 → Use After Free → 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: a standard category for the underlying weakness.
CWE-416 ↗

CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.

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.
CWE-416
A

Official authority intelligence

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

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

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

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

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

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

d?id=CVE-2026-64064 Référence CVE CVE-2026-64065 https://www.cve.org/CVERecord?id=CVE-2026-64065 Référence CVE CVE-2026-64066 https://www.cve.org/CVERecord?id=CVE-2026-64066 Référence CVE CVE-2026-64067 https://www.cve.org/CVERecord?id=CVE-2026-64067 Référence CVE CVE-2026-64068 https://www.cve.org/CVERecord?id=CVE-2026-64068 Référence CVE CVE-2026-64069 https://www.cve.org/CVERecord?id=CVE-2026-64069 Référence CVE CVE-2026-64070 https://www.cve.org/CVERecord?id=CVE-2026-64070 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64072 https://www.cve.org/CVERecord?id=CVE-2026-64072 Référence CVE CVE-2026-64073 https://www.cve.org/CVERecord?id=CVE-2026-64073 Référence CVE CVE-2026-64074 https://www.cve.org/CVERecord?id=CVE-2026-64074 Référence CVE CVE-2026-64075 https://www.cve.org/CVERecord?id=CVE-2026-64075 Référence CVE CVE-2026-64076 https://www.cve.org/CVERecord?id=CVE-2026-64076 Référence CVE CVE-2026-64077 https://www.cve.org/CVERecord?id=CVE-2026-64077 Référence CVE CVE-2026-64078 https://www.cve.org/CVERecord?id=CVE-2026-64078 Référence CVE CVE-2026-64079 https://www.cve.org/CVERecord?id=CVE-2026-64079 Référence CVE CVE-2026-64080 https://www.cve.org/CVERecord?id=CVE-2026-64080 Référence CVE CVE-2026-64081 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64047 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64051 https://www.cve.org/CVERecord?id=CVE-2026-64051 Référence CVE CVE-2026-64052 https://www.cve.org/CVERecord?id=CVE-2026-64052 Référence CVE CVE-2026-64053 https://www.cve.org/CVERecord?id=CVE-2026-64053 Référence CVE CVE-2026-64054 https://www.cve.org/CVERecord?id=CVE-2026-64054 Référence CVE CVE-2026-64055 https://www.cve.org/CVERecord?id=CVE-2026-64055 Référence CVE CVE-2026-64056 https://www.cve.org/CVERecord?id=CVE-2026-64056 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64073 https://www.cve.org/CVERecord?id=CVE-2026-64073 Référence CVE CVE-2026-64083 https://www.cve.org/CVERecord?id=CVE-2026-64083 Référence CVE CVE-2026-64084 https://www.cve.org/CVERecord?id=CVE-2026-64084 Référence CVE CVE-2026-64085 https://www.cve.org/CVERecord?id=CVE-2026-64085 Référence CVE CVE-2026-64086 https://www.cve.org/CVERecord?id=CVE-2026-64086 Référence CVE CVE-2026-64087 https://www.cve.org/CVERecord?id=CVE-2026-64087 Référence CVE CVE-2026-64088 https://www.cve.org/CVERecord?id=CVE-2026-64088 Référence CVE CVE-2026-64089 https://www.cve.org/CVERecord?id=CVE-2026-64089 Référence CVE CVE-2026-64093 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64064 Référence CVE CVE-2026-64065 https://www.cve.org/CVERecord?id=CVE-2026-64065 Référence CVE CVE-2026-64066 https://www.cve.org/CVERecord?id=CVE-2026-64066 Référence CVE CVE-2026-64067 https://www.cve.org/CVERecord?id=CVE-2026-64067 Référence CVE CVE-2026-64068 https://www.cve.org/CVERecord?id=CVE-2026-64068 Référence CVE CVE-2026-64069 https://www.cve.org/CVERecord?id=CVE-2026-64069 Référence CVE CVE-2026-64070 https://www.cve.org/CVERecord?id=CVE-2026-64070 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64072 https://www.cve.org/CVERecord?id=CVE-2026-64072 Référence CVE CVE-2026-64073 https://www.cve.org/CVERecord?id=CVE-2026-64073 Référence CVE CVE-2026-64074 https://www.cve.org/CVERecord?id=CVE-2026-64074 Référence CVE CVE-2026-64075 https://www.cve.org/CVERecord?id=CVE-2026-64075 Référence CVE CVE-2026-64076 https://www.cve.org/CVERecord?id=CVE-2026-64076 Référence CVE CVE-2026-64077 https://www.cve.org/CVERecord?id=CVE-2026-64077 Référence CVE CVE-2026-64078 https://www.cve.org/CVERecord?id=CVE-2026-64078 Référence CVE CVE-2026-64079 https://www.cve.org/CVERecord?id=CVE-2026-64079 Référence CVE CVE-2026-64080 https://www.cve.org/CVERecord?id=CVE-2026-64080 Référence CVE CVE-2026-64081 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64039 https://www.cve.org/CVERecord?id=CVE-2026-64039 Référence CVE CVE-2026-64047 https://www.cve.org/CVERecord?id=CVE-2026-64047 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64051 https://www.cve.org/CVERecord?id=CVE-2026-64051 Référence CVE CVE-2026-64052 https://www.cve.org/CVERecord?id=CVE-2026-64052 Référence CVE CVE-2026-64055 https://www.cve.org/CVERecord?id=CVE-2026-64055 Référence CVE CVE-2026-64056 https://www.cve.org/CVERecord?id=CVE-2026-64056 Référence CVE CVE-2026-64073 https://www.cve.org/CVERecord?id=CVE-2026-64073 Référence CVE CVE-2026-64083 https://www.cve.org/CVERecord?id=CVE-2026-64083 Référence CVE CVE-2026-64084 https://www.cve.org/CVERecord?id=CVE-2026-64084 Référence CVE CVE-2026-64085 https://www.cve.org/CVERecord?id=CVE-2026-64085 Référence CVE CVE-2026-64086 https://www.cve.org/CVERecord?id=CVE-2026-64086 Référence CVE CVE-2026-64087 https://www.cve.org/CVERecord?id=CVE-2026-64087 Référence CVE CVE-2026-64088 https://www.cve.org/CVERecord?id=CVE-2026-64088 Référence CVE CVE-2026-64097 https://www.cve.org/CVERecord?id=CVE-2026-64097 Référence CVE CVE-2026-64098 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64034 Référence CVE CVE-2026-64039 https://www.cve.org/CVERecord?id=CVE-2026-64039 Référence CVE CVE-2026-64046 https://www.cve.org/CVERecord?id=CVE-2026-64046 Référence CVE CVE-2026-64047 https://www.cve.org/CVERecord?id=CVE-2026-64047 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64051 https://www.cve.org/CVERecord?id=CVE-2026-64051 Référence CVE CVE-2026-64055 https://www.cve.org/CVERecord?id=CVE-2026-64055 Référence CVE CVE-2026-64056 https://www.cve.org/CVERecord?id=CVE-2026-64056 Référence CVE CVE-2026-64064 https://www.cve.org/CVERecord?id=CVE-2026-64064 Référence CVE CVE-2026-64073 https://www.cve.org/CVERecord?id=CVE-2026-64073 Référence CVE CVE-2026-64076 https://www.cve.org/CVERecord?id=CVE-2026-64076 Référence CVE CVE-2026-64077 https://www.cve.org/CVERecord?id=CVE-2026-64077 Référence CVE CVE-2026-64082 https://www.cve.org/CVERecord?id=CVE-2026-64082 Référence CVE CVE-2026-64083 https://www.cve.org/CVERecord?id=CVE-2026-64083 Référence CVE CVE-2026-64084 https://www.cve.org/CVERecord?id=CVE-2026-64084 Référence CVE CVE-2026-64085 https://www.cve.org/CVERecord?id=CVE-2026-64085 Référence CVE CVE-2026-64086 https://www.cve.org/CVERecord?id=CVE-2026-64086 Référence CVE CVE-2026-64087 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64064 Référence CVE CVE-2026-64065 https://www.cve.org/CVERecord?id=CVE-2026-64065 Référence CVE CVE-2026-64066 https://www.cve.org/CVERecord?id=CVE-2026-64066 Référence CVE CVE-2026-64067 https://www.cve.org/CVERecord?id=CVE-2026-64067 Référence CVE CVE-2026-64068 https://www.cve.org/CVERecord?id=CVE-2026-64068 Référence CVE CVE-2026-64069 https://www.cve.org/CVERecord?id=CVE-2026-64069 Référence CVE CVE-2026-64070 https://www.cve.org/CVERecord?id=CVE-2026-64070 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64072 https://www.cve.org/CVERecord?id=CVE-2026-64072 Référence CVE CVE-2026-64073 https://www.cve.org/CVERecord?id=CVE-2026-64073 Référence CVE CVE-2026-64074 https://www.cve.org/CVERecord?id=CVE-2026-64074 Référence CVE CVE-2026-64075 https://www.cve.org/CVERecord?id=CVE-2026-64075 Référence CVE CVE-2026-64076 https://www.cve.org/CVERecord?id=CVE-2026-64076 Référence CVE CVE-2026-64077 https://www.cve.org/CVERecord?id=CVE-2026-64077 Référence CVE CVE-2026-64078 https://www.cve.org/CVERecord?id=CVE-2026-64078 Référence CVE CVE-2026-64079 https://www.cve.org/CVERecord?id=CVE-2026-64079 Référence CVE CVE-2026-64080 https://www.cve.org/CVERecord?id=CVE-2026-64080 Référence CVE CVE-2026-64081 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64033 Référence CVE CVE-2026-64034 https://www.cve.org/CVERecord?id=CVE-2026-64034 Référence CVE CVE-2026-64039 https://www.cve.org/CVERecord?id=CVE-2026-64039 Référence CVE CVE-2026-64047 https://www.cve.org/CVERecord?id=CVE-2026-64047 Référence CVE CVE-2026-64048 https://www.cve.org/CVERecord?id=CVE-2026-64048 Référence CVE CVE-2026-64051 https://www.cve.org/CVERecord?id=CVE-2026-64051 Référence CVE CVE-2026-64052 https://www.cve.org/CVERecord?id=CVE-2026-64052 Référence CVE CVE-2026-64055 https://www.cve.org/CVERecord?id=CVE-2026-64055 Référence CVE CVE-2026-64056 https://www.cve.org/CVERecord?id=CVE-2026-64056 Référence CVE CVE-2026-64073 https://www.cve.org/CVERecord?id=CVE-2026-64073 Référence CVE CVE-2026-64083 https://www.cve.org/CVERecord?id=CVE-2026-64083 Référence CVE CVE-2026-64084 https://www.cve.org/CVERecord?id=CVE-2026-64084 Référence CVE CVE-2026-64085 https://www.cve.org/CVERecord?id=CVE-2026-64085 Référence CVE CVE-2026-64086 https://www.cve.org/CVERecord?id=CVE-2026-64086 Référence CVE CVE-2026-64087 https://www.cve.org/CVERecord?id=CVE-2026-64087 Référence CVE CVE-2026-64088 https://www.cve.org/CVERecord?id=CVE-2026-64088 Référence CVE CVE-2026-64097 https://www.cve.org/CVERecord?id=CVE-2026-64097 Référence CVE CVE-2026-64098 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64064 Référence CVE CVE-2026-64065 https://www.cve.org/CVERecord?id=CVE-2026-64065 Référence CVE CVE-2026-64066 https://www.cve.org/CVERecord?id=CVE-2026-64066 Référence CVE CVE-2026-64067 https://www.cve.org/CVERecord?id=CVE-2026-64067 Référence CVE CVE-2026-64068 https://www.cve.org/CVERecord?id=CVE-2026-64068 Référence CVE CVE-2026-64069 https://www.cve.org/CVERecord?id=CVE-2026-64069 Référence CVE CVE-2026-64070 https://www.cve.org/CVERecord?id=CVE-2026-64070 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64072 https://www.cve.org/CVERecord?id=CVE-2026-64072 Référence CVE CVE-2026-64073 https://www.cve.org/CVERecord?id=CVE-2026-64073 Référence CVE CVE-2026-64074 https://www.cve.org/CVERecord?id=CVE-2026-64074 Référence CVE CVE-2026-64075 https://www.cve.org/CVERecord?id=CVE-2026-64075 Référence CVE CVE-2026-64076 https://www.cve.org/CVERecord?id=CVE-2026-64076 Référence CVE CVE-2026-64077 https://www.cve.org/CVERecord?id=CVE-2026-64077 Référence CVE CVE-2026-64078 https://www.cve.org/CVERecord?id=CVE-2026-64078 Référence CVE CVE-2026-64079 https://www.cve.org/CVERecord?id=CVE-2026-64079 Référence CVE CVE-2026-64080 https://www.cve.org/CVERecord?id=CVE-2026-64080 Référence CVE CVE-2026-64081 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-64064 Référence CVE CVE-2026-64065 https://www.cve.org/CVERecord?id=CVE-2026-64065 Référence CVE CVE-2026-64066 https://www.cve.org/CVERecord?id=CVE-2026-64066 Référence CVE CVE-2026-64067 https://www.cve.org/CVERecord?id=CVE-2026-64067 Référence CVE CVE-2026-64068 https://www.cve.org/CVERecord?id=CVE-2026-64068 Référence CVE CVE-2026-64069 https://www.cve.org/CVERecord?id=CVE-2026-64069 Référence CVE CVE-2026-64070 https://www.cve.org/CVERecord?id=CVE-2026-64070 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64072 https://www.cve.org/CVERecord?id=CVE-2026-64072 Référence CVE CVE-2026-64073 https://www.cve.org/CVERecord?id=CVE-2026-64073 Référence CVE CVE-2026-64074 https://www.cve.org/CVERecord?id=CVE-2026-64074 Référence CVE CVE-2026-64075 https://www.cve.org/CVERecord?id=CVE-2026-64075 Référence CVE CVE-2026-64076 https://www.cve.org/CVERecord?id=CVE-2026-64076 Référence CVE CVE-2026-64077 https://www.cve.org/CVERecord?id=CVE-2026-64077 Référence CVE CVE-2026-64078 https://www.cve.org/CVERecord?id=CVE-2026-64078 Référence CVE CVE-2026-64079 https://www.cve.org/CVERecord?id=CVE-2026-64079 Référence CVE CVE-2026-64080 https://www.cve.org/CVERecord?id=CVE-2026-64080 Référence CVE CVE-2026-64081 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-64064 Référence CVE CVE-2026-64065 https://www.cve.org/CVERecord?id=CVE-2026-64065 Référence CVE CVE-2026-64066 https://www.cve.org/CVERecord?id=CVE-2026-64066 Référence CVE CVE-2026-64067 https://www.cve.org/CVERecord?id=CVE-2026-64067 Référence CVE CVE-2026-64068 https://www.cve.org/CVERecord?id=CVE-2026-64068 Référence CVE CVE-2026-64069 https://www.cve.org/CVERecord?id=CVE-2026-64069 Référence CVE CVE-2026-64070 https://www.cve.org/CVERecord?id=CVE-2026-64070 Référence CVE CVE-2026-64071 https://www.cve.org/CVERecord?id=CVE-2026-64071 Référence CVE CVE-2026-64072 https://www.cve.org/CVERecord?id=CVE-2026-64072 Référence CVE CVE-2026-64073 https://www.cve.org/CVERecord?id=CVE-2026-64073 Référence CVE CVE-2026-64074 https://www.cve.org/CVERecord?id=CVE-2026-64074 Référence CVE CVE-2026-64075 https://www.cve.org/CVERecord?id=CVE-2026-64075 Référence CVE CVE-2026-64076 https://www.cve.org/CVERecord?id=CVE-2026-64076 Référence CVE CVE-2026-64077 https://www.cve.org/CVERecord?id=CVE-2026-64077 Référence CVE CVE-2026-64078 https://www.cve.org/CVERecord?id=CVE-2026-64078 Référence CVE CVE-2026-64079 https://www.cve.org/CVERecord?id=CVE-2026-64079 Référence CVE CVE-2026-64080 https://www.cve.org/CVERecord?id=CVE-2026-64080 Référence CVE CVE-2026-64081 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-031821LinuxのLinux Kernelにおける解放済みメモリの使用に関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。irq_work: PREEMPT_RT環境でのirq_work_single()におけるuse-after-freeの問題の修正です。PREEMPT_RTでは、非HARDなirq_workがrun_irq_workd()経由でCPUごとのkthreadで実行されるため、irq_work_sync()はBUSY==0を待つためにrcuwait()を使用します。irq_work_single()がatomic_cmpxchg()でBUSYをクリアした後も、irq_work_is_hard()およびrcuwait_wake_up()のために@workへの参照が続きます。別のCPUのirq_work_sync()呼び出し元がBUSYクリア後に実行されると、すぐにBUSY==0を観測してreturnし、これらのアクセスが完了する前にworkを解放してしまうため、use-after-freeが発生します。この問題は、run_irq_workd()をguard(rcu)()でラップし、irq_work_single()の処理全体をRCU読み取り側のクリティカルセクション内に収めることで修正しました。さらに、irq_work_sync()のrcuwait_wait_event()の後にsynchronize_rcu()を追加し、呼び出し元がRCU猶予期間を待ってから戻るようにして、premature freeを防止しています。

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.16, 6.1.175 ≤ 6.1.*, 6.6.142 ≤ 6.6.*, 6.12.92 ≤ 6.12.*, 6.18.34 ≤ 6.18.*, 7.0.11 ≤ 7.0.*, 7.1 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 19 Jul 2026 · Last source change 5 Aug 2026, 12:38 UTC · CWE-416 · Use After Free

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-45646
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added patch: git.kernel.org/18c0456ea2615b1a743a6db739c74411c3b42bc6; added patch: git.kernel.org/2dc79362302922cb18f35e262712b5e58de65442; 4 further additions.
    Before
    remediation: git.kernel.org/2dc79362302922cb18f35e262712b5e58de65442
    After
    patch: git.kernel.org/18c0456ea2615b1a743a6db739c74411c3b42bc6 · patch: git.kernel.org/2dc79362302922cb18f35e262712b5e58de65442 · patch: git.kernel.org/684a78183c54c23e70d1cba320f7fc184604210b · 4 more references
    git.kernel.org ↗
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-45646↗Vendor CSAF · SUSE Product Security Team↗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-64073 · cve.blacktree.nl