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

net/sched: taprio: fix use-after-free in advance_sched() on schedule switch

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.17% 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.10-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-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-53011 · CSAF 2.0 · revision 13 · interimSUSE Product Security TeamCVE-2026-53011
230 known affected

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

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP7
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP7
  • cluster-md-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • dlm-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • gfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • ocfs2-kmp-default as component of SUSE Linux Enterprise High Availability Extension 15 SP7
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
Summary
In the Linux kernel, the following vulnerability has been resolved: net/sched: taprio: fix use-after-free in advance_sched() on schedule switch In advance_sched(), when should_change_schedules() returns true, switch_schedules() is called to promote the admin schedule to oper. switch_schedules() queues the old oper schedule for RCU freeing via call_rcu(), but 'next' still points into an entry of the old oper schedule. The subsequent 'next->end_time = end_time' and rcu_assign_pointer(q->current_entry, next) are use-after-free. Fix this by selecting 'next' from the new oper schedule immediately after switch_schedules(), and using its pre-calculated end_time. setup_first_end_time() sets the first entry's end_time to base_time + interval when the schedule is installed, so the value is already correct. The deleted 'end_time = sched_base_time(admin)' assignment was also harmful independently: it would overwrite the new first entry's pre-calculated end_time with just base_time.
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-38879

No EUVD known-exploited evidence

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

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

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

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: net/sched: taprio: fix use-after-free in advance_sched() on schedule switch In advance_sched(), when should_change_schedules() returns true, switch_schedules() is called to promote the admin schedule to oper. switch_schedules() queues the old oper schedule for RCU freeing via call_rcu(), but 'next' still points into an entry of the old oper schedule. The subsequent 'next->end_time = end_time' and rcu_assign_pointer(q->current_entry, next) are use-after-free. Fix this by selecting 'next' from the new oper schedule immediately after switch_schedules(), and using its pre-calculated end_time. setup_first_end_time() sets the first entry's end_time to base_time + interval when the schedule is installed, so the value is already correct. The deleted 'end_time = sched_base_time(admin)' assignment was also harmful independently: it would overwrite the new first entry's pre-calculated end_time with just base_time.

What

In the Linux kernel, the following vulnerability has been resolved: net/sched: taprio: fix use-after-free in advance_sched() on schedule switch In advance_sched(), when should_change_schedules() returns true, switch_schedules() is called to promote the admin schedule to oper. switch_schedules() queues the old oper schedule for RCU freeing via call_rcu(), but 'next' still points into an entry of the old oper schedule. The subsequent 'next->end_time = end_time' and rcu_assign_pointer(q->current_entry, next) are use-after-free. Fix this by selecting 'next' from the new oper schedule immediately after switch_schedules(), and using its pre-calculated end_time. setup_first_end_time() sets the first entry's end_time to base_time + interval when the schedule is installed, so the value is already correct. The deleted 'end_time = sched_base_time(admin)' assignment was also harmful independently: it would overwrite the new first entry's pre-calculated end_time with just base_time.

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: net/sched: taprio: fix use-after-free in advance_sched() on schedule switch In advance_sched(), when should_change_schedules() returns true, switch_schedules() is called to promote the admin schedule to oper. switch_schedules() queues the old oper schedule for RCU freeing via call_rcu(), but 'next' still points into an entry of the old oper schedule. The subsequent 'next->end_time = end_time' and rcu_assign_pointer(q->current_entry, next) are use-after-free. Fix this by selecting 'next' from the new oper schedule immediately after switch_schedules(), and using its pre-calculated end_time. setup_first_end_time() sets the first entry's end_time to base_time + interval when the schedule is installed, so the value is already correct. The deleted 'end_time = sched_base_time(admin)' assignment was also harmful independently: it would overwrite the new first entry's pre-calculated end_time with just base_time.

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-2077Linux Kernel: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen und weitere, nicht näher spezifizierte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260701Security Bulletin 1 July 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 1 July 2026, published on 1 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-53002 Référence CVE CVE-2026-53003 https://www.cve.org/CVERecord?id=CVE-2026-53003 Référence CVE CVE-2026-53004 https://www.cve.org/CVERecord?id=CVE-2026-53004 Référence CVE CVE-2026-53005 https://www.cve.org/CVERecord?id=CVE-2026-53005 Référence CVE CVE-2026-53006 https://www.cve.org/CVERecord?id=CVE-2026-53006 Référence CVE CVE-2026-53007 https://www.cve.org/CVERecord?id=CVE-2026-53007 Référence CVE CVE-2026-53008 https://www.cve.org/CVERecord?id=CVE-2026-53008 Référence CVE CVE-2026-53009 https://www.cve.org/CVERecord?id=CVE-2026-53009 Référence CVE CVE-2026-53010 https://www.cve.org/CVERecord?id=CVE-2026-53010 Référence CVE CVE-2026-53011 https://www.cve.org/CVERecord?id=CVE-2026-53011 Référence CVE CVE-2026-53012 https://www.cve.org/CVERecord?id=CVE-2026-53012 Référence CVE CVE-2026-53013 https://www.cve.org/CVERecord?id=CVE-2026-53013 Référence CVE CVE-2026-53014 https://www.cve.org/CVERecord?id=CVE-2026-53014 Référence CVE CVE-2026-53015 https://www.cve.org/CVERecord?id=CVE-2026-53015 Référence CVE CVE-2026-53016 https://www.cve.org/CVERecord?id=CVE-2026-53016 Référence CVE CVE-2026-53017 https://www.cve.org/CVERecord?id=CVE-2026-53017 Référence CVE CVE-2026-53018 https://www.cve.org/CVERecord?id=CVE-2026-53018 Référence CVE CVE-2026-53019 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-53002 Référence CVE CVE-2026-53003 https://www.cve.org/CVERecord?id=CVE-2026-53003 Référence CVE CVE-2026-53004 https://www.cve.org/CVERecord?id=CVE-2026-53004 Référence CVE CVE-2026-53005 https://www.cve.org/CVERecord?id=CVE-2026-53005 Référence CVE CVE-2026-53006 https://www.cve.org/CVERecord?id=CVE-2026-53006 Référence CVE CVE-2026-53007 https://www.cve.org/CVERecord?id=CVE-2026-53007 Référence CVE CVE-2026-53008 https://www.cve.org/CVERecord?id=CVE-2026-53008 Référence CVE CVE-2026-53009 https://www.cve.org/CVERecord?id=CVE-2026-53009 Référence CVE CVE-2026-53010 https://www.cve.org/CVERecord?id=CVE-2026-53010 Référence CVE CVE-2026-53011 https://www.cve.org/CVERecord?id=CVE-2026-53011 Référence CVE CVE-2026-53012 https://www.cve.org/CVERecord?id=CVE-2026-53012 Référence CVE CVE-2026-53013 https://www.cve.org/CVERecord?id=CVE-2026-53013 Référence CVE CVE-2026-53014 https://www.cve.org/CVERecord?id=CVE-2026-53014 Référence CVE CVE-2026-53015 https://www.cve.org/CVERecord?id=CVE-2026-53015 Référence CVE CVE-2026-53016 https://www.cve.org/CVERecord?id=CVE-2026-53016 Référence CVE CVE-2026-53017 https://www.cve.org/CVERecord?id=CVE-2026-53017 Référence CVE CVE-2026-53018 https://www.cve.org/CVERecord?id=CVE-2026-53018 Référence CVE CVE-2026-53019 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-53002 Référence CVE CVE-2026-53003 https://www.cve.org/CVERecord?id=CVE-2026-53003 Référence CVE CVE-2026-53004 https://www.cve.org/CVERecord?id=CVE-2026-53004 Référence CVE CVE-2026-53005 https://www.cve.org/CVERecord?id=CVE-2026-53005 Référence CVE CVE-2026-53006 https://www.cve.org/CVERecord?id=CVE-2026-53006 Référence CVE CVE-2026-53007 https://www.cve.org/CVERecord?id=CVE-2026-53007 Référence CVE CVE-2026-53008 https://www.cve.org/CVERecord?id=CVE-2026-53008 Référence CVE CVE-2026-53009 https://www.cve.org/CVERecord?id=CVE-2026-53009 Référence CVE CVE-2026-53010 https://www.cve.org/CVERecord?id=CVE-2026-53010 Référence CVE CVE-2026-53011 https://www.cve.org/CVERecord?id=CVE-2026-53011 Référence CVE CVE-2026-53012 https://www.cve.org/CVERecord?id=CVE-2026-53012 Référence CVE CVE-2026-53013 https://www.cve.org/CVERecord?id=CVE-2026-53013 Référence CVE CVE-2026-53014 https://www.cve.org/CVERecord?id=CVE-2026-53014 Référence CVE CVE-2026-53015 https://www.cve.org/CVERecord?id=CVE-2026-53015 Référence CVE CVE-2026-53016 https://www.cve.org/CVERecord?id=CVE-2026-53016 Référence CVE CVE-2026-53017 https://www.cve.org/CVERecord?id=CVE-2026-53017 Référence CVE CVE-2026-53018 https://www.cve.org/CVERecord?id=CVE-2026-53018 Référence CVE CVE-2026-53019 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52993 Référence CVE CVE-2026-52995 https://www.cve.org/CVERecord?id=CVE-2026-52995 Référence CVE CVE-2026-52998 https://www.cve.org/CVERecord?id=CVE-2026-52998 Référence CVE CVE-2026-52999 https://www.cve.org/CVERecord?id=CVE-2026-52999 Référence CVE CVE-2026-53001 https://www.cve.org/CVERecord?id=CVE-2026-53001 Référence CVE CVE-2026-53002 https://www.cve.org/CVERecord?id=CVE-2026-53002 Référence CVE CVE-2026-53003 https://www.cve.org/CVERecord?id=CVE-2026-53003 Référence CVE CVE-2026-53004 https://www.cve.org/CVERecord?id=CVE-2026-53004 Référence CVE CVE-2026-53006 https://www.cve.org/CVERecord?id=CVE-2026-53006 Référence CVE CVE-2026-53011 https://www.cve.org/CVERecord?id=CVE-2026-53011 Référence CVE CVE-2026-53012 https://www.cve.org/CVERecord?id=CVE-2026-53012 Référence CVE CVE-2026-53016 https://www.cve.org/CVERecord?id=CVE-2026-53016 Référence CVE CVE-2026-53021 https://www.cve.org/CVERecord?id=CVE-2026-53021 Référence CVE CVE-2026-53022 https://www.cve.org/CVERecord?id=CVE-2026-53022 Référence CVE CVE-2026-53023 https://www.cve.org/CVERecord?id=CVE-2026-53023 Référence CVE CVE-2026-53037 https://www.cve.org/CVERecord?id=CVE-2026-53037 Référence CVE CVE-2026-53039 https://www.cve.org/CVERecord?id=CVE-2026-53039 Référence CVE CVE-2026-53040 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52984 Référence CVE CVE-2026-52986 https://www.cve.org/CVERecord?id=CVE-2026-52986 Référence CVE CVE-2026-52988 https://www.cve.org/CVERecord?id=CVE-2026-52988 Référence CVE CVE-2026-52991 https://www.cve.org/CVERecord?id=CVE-2026-52991 Référence CVE CVE-2026-52998 https://www.cve.org/CVERecord?id=CVE-2026-52998 Référence CVE CVE-2026-52999 https://www.cve.org/CVERecord?id=CVE-2026-52999 Référence CVE CVE-2026-53000 https://www.cve.org/CVERecord?id=CVE-2026-53000 Référence CVE CVE-2026-53002 https://www.cve.org/CVERecord?id=CVE-2026-53002 Référence CVE CVE-2026-53006 https://www.cve.org/CVERecord?id=CVE-2026-53006 Référence CVE CVE-2026-53011 https://www.cve.org/CVERecord?id=CVE-2026-53011 Référence CVE CVE-2026-53012 https://www.cve.org/CVERecord?id=CVE-2026-53012 Référence CVE CVE-2026-53032 https://www.cve.org/CVERecord?id=CVE-2026-53032 Référence CVE CVE-2026-53062 https://www.cve.org/CVERecord?id=CVE-2026-53062 Référence CVE CVE-2026-53063 https://www.cve.org/CVERecord?id=CVE-2026-53063 Référence CVE CVE-2026-53064 https://www.cve.org/CVERecord?id=CVE-2026-53064 Référence CVE CVE-2026-53069 https://www.cve.org/CVERecord?id=CVE-2026-53069 Référence CVE CVE-2026-53074 https://www.cve.org/CVERecord?id=CVE-2026-53074 Référence CVE CVE-2026-53083 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-53002 Référence CVE CVE-2026-53003 https://www.cve.org/CVERecord?id=CVE-2026-53003 Référence CVE CVE-2026-53004 https://www.cve.org/CVERecord?id=CVE-2026-53004 Référence CVE CVE-2026-53005 https://www.cve.org/CVERecord?id=CVE-2026-53005 Référence CVE CVE-2026-53006 https://www.cve.org/CVERecord?id=CVE-2026-53006 Référence CVE CVE-2026-53007 https://www.cve.org/CVERecord?id=CVE-2026-53007 Référence CVE CVE-2026-53008 https://www.cve.org/CVERecord?id=CVE-2026-53008 Référence CVE CVE-2026-53009 https://www.cve.org/CVERecord?id=CVE-2026-53009 Référence CVE CVE-2026-53010 https://www.cve.org/CVERecord?id=CVE-2026-53010 Référence CVE CVE-2026-53011 https://www.cve.org/CVERecord?id=CVE-2026-53011 Référence CVE CVE-2026-53012 https://www.cve.org/CVERecord?id=CVE-2026-53012 Référence CVE CVE-2026-53013 https://www.cve.org/CVERecord?id=CVE-2026-53013 Référence CVE CVE-2026-53014 https://www.cve.org/CVERecord?id=CVE-2026-53014 Référence CVE CVE-2026-53015 https://www.cve.org/CVERecord?id=CVE-2026-53015 Référence CVE CVE-2026-53016 https://www.cve.org/CVERecord?id=CVE-2026-53016 Référence CVE CVE-2026-53017 https://www.cve.org/CVERecord?id=CVE-2026-53017 Référence CVE CVE-2026-53018 https://www.cve.org/CVERecord?id=CVE-2026-53018 Référence CVE CVE-2026-53019 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52998 Référence CVE CVE-2026-52999 https://www.cve.org/CVERecord?id=CVE-2026-52999 Référence CVE CVE-2026-53000 https://www.cve.org/CVERecord?id=CVE-2026-53000 Référence CVE CVE-2026-53002 https://www.cve.org/CVERecord?id=CVE-2026-53002 Référence CVE CVE-2026-53003 https://www.cve.org/CVERecord?id=CVE-2026-53003 Référence CVE CVE-2026-53004 https://www.cve.org/CVERecord?id=CVE-2026-53004 Référence CVE CVE-2026-53005 https://www.cve.org/CVERecord?id=CVE-2026-53005 Référence CVE CVE-2026-53006 https://www.cve.org/CVERecord?id=CVE-2026-53006 Référence CVE CVE-2026-53009 https://www.cve.org/CVERecord?id=CVE-2026-53009 Référence CVE CVE-2026-53011 https://www.cve.org/CVERecord?id=CVE-2026-53011 Référence CVE CVE-2026-53012 https://www.cve.org/CVERecord?id=CVE-2026-53012 Référence CVE CVE-2026-53013 https://www.cve.org/CVERecord?id=CVE-2026-53013 Référence CVE CVE-2026-53014 https://www.cve.org/CVERecord?id=CVE-2026-53014 Référence CVE CVE-2026-53016 https://www.cve.org/CVERecord?id=CVE-2026-53016 Référence CVE CVE-2026-53022 https://www.cve.org/CVERecord?id=CVE-2026-53022 Référence CVE CVE-2026-53032 https://www.cve.org/CVERecord?id=CVE-2026-53032 Référence CVE CVE-2026-53035 https://www.cve.org/CVERecord?id=CVE-2026-53035 Référence CVE CVE-2026-53037 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52993 Référence CVE CVE-2026-52995 https://www.cve.org/CVERecord?id=CVE-2026-52995 Référence CVE CVE-2026-52998 https://www.cve.org/CVERecord?id=CVE-2026-52998 Référence CVE CVE-2026-52999 https://www.cve.org/CVERecord?id=CVE-2026-52999 Référence CVE CVE-2026-53001 https://www.cve.org/CVERecord?id=CVE-2026-53001 Référence CVE CVE-2026-53002 https://www.cve.org/CVERecord?id=CVE-2026-53002 Référence CVE CVE-2026-53003 https://www.cve.org/CVERecord?id=CVE-2026-53003 Référence CVE CVE-2026-53004 https://www.cve.org/CVERecord?id=CVE-2026-53004 Référence CVE CVE-2026-53006 https://www.cve.org/CVERecord?id=CVE-2026-53006 Référence CVE CVE-2026-53011 https://www.cve.org/CVERecord?id=CVE-2026-53011 Référence CVE CVE-2026-53012 https://www.cve.org/CVERecord?id=CVE-2026-53012 Référence CVE CVE-2026-53016 https://www.cve.org/CVERecord?id=CVE-2026-53016 Référence CVE CVE-2026-53021 https://www.cve.org/CVERecord?id=CVE-2026-53021 Référence CVE CVE-2026-53022 https://www.cve.org/CVERecord?id=CVE-2026-53022 Référence CVE CVE-2026-53023 https://www.cve.org/CVERecord?id=CVE-2026-53023 Référence CVE CVE-2026-53037 https://www.cve.org/CVERecord?id=CVE-2026-53037 Référence CVE CVE-2026-53039 https://www.cve.org/CVERecord?id=CVE-2026-53039 Référence CVE CVE-2026-53040 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-53002 Référence CVE CVE-2026-53003 https://www.cve.org/CVERecord?id=CVE-2026-53003 Référence CVE CVE-2026-53004 https://www.cve.org/CVERecord?id=CVE-2026-53004 Référence CVE CVE-2026-53005 https://www.cve.org/CVERecord?id=CVE-2026-53005 Référence CVE CVE-2026-53006 https://www.cve.org/CVERecord?id=CVE-2026-53006 Référence CVE CVE-2026-53007 https://www.cve.org/CVERecord?id=CVE-2026-53007 Référence CVE CVE-2026-53008 https://www.cve.org/CVERecord?id=CVE-2026-53008 Référence CVE CVE-2026-53009 https://www.cve.org/CVERecord?id=CVE-2026-53009 Référence CVE CVE-2026-53010 https://www.cve.org/CVERecord?id=CVE-2026-53010 Référence CVE CVE-2026-53011 https://www.cve.org/CVERecord?id=CVE-2026-53011 Référence CVE CVE-2026-53012 https://www.cve.org/CVERecord?id=CVE-2026-53012 Référence CVE CVE-2026-53013 https://www.cve.org/CVERecord?id=CVE-2026-53013 Référence CVE CVE-2026-53014 https://www.cve.org/CVERecord?id=CVE-2026-53014 Référence CVE CVE-2026-53015 https://www.cve.org/CVERecord?id=CVE-2026-53015 Référence CVE CVE-2026-53016 https://www.cve.org/CVERecord?id=CVE-2026-53016 Référence CVE CVE-2026-53017 https://www.cve.org/CVERecord?id=CVE-2026-53017 Référence CVE CVE-2026-53018 https://www.cve.org/CVERecord?id=CVE-2026-53018 Référence CVE CVE-2026-53019 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-53002 Référence CVE CVE-2026-53003 https://www.cve.org/CVERecord?id=CVE-2026-53003 Référence CVE CVE-2026-53004 https://www.cve.org/CVERecord?id=CVE-2026-53004 Référence CVE CVE-2026-53005 https://www.cve.org/CVERecord?id=CVE-2026-53005 Référence CVE CVE-2026-53006 https://www.cve.org/CVERecord?id=CVE-2026-53006 Référence CVE CVE-2026-53007 https://www.cve.org/CVERecord?id=CVE-2026-53007 Référence CVE CVE-2026-53008 https://www.cve.org/CVERecord?id=CVE-2026-53008 Référence CVE CVE-2026-53009 https://www.cve.org/CVERecord?id=CVE-2026-53009 Référence CVE CVE-2026-53010 https://www.cve.org/CVERecord?id=CVE-2026-53010 Référence CVE CVE-2026-53011 https://www.cve.org/CVERecord?id=CVE-2026-53011 Référence CVE CVE-2026-53012 https://www.cve.org/CVERecord?id=CVE-2026-53012 Référence CVE CVE-2026-53013 https://www.cve.org/CVERecord?id=CVE-2026-53013 Référence CVE CVE-2026-53014 https://www.cve.org/CVERecord?id=CVE-2026-53014 Référence CVE CVE-2026-53015 https://www.cve.org/CVERecord?id=CVE-2026-53015 Référence CVE CVE-2026-53016 https://www.cve.org/CVERecord?id=CVE-2026-53016 Référence CVE CVE-2026-53017 https://www.cve.org/CVERecord?id=CVE-2026-53017 Référence CVE CVE-2026-53018 https://www.cve.org/CVERecord?id=CVE-2026-53018 Référence CVE CVE-2026-53019 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0866Multiples vulnérabilités dans Microsoft Azure Linux

u 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52986 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52989 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52993 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52998 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-52999 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53002 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53003 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53006 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53011 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53012 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53013 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53021 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53022 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53023 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53032 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53034 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linux CVE-2026-53035 du 27 juin 2026 Bulletin de sécurité Microsoft Azure Linu

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

d?id=CVE-2026-52993 Référence CVE CVE-2026-52995 https://www.cve.org/CVERecord?id=CVE-2026-52995 Référence CVE CVE-2026-52998 https://www.cve.org/CVERecord?id=CVE-2026-52998 Référence CVE CVE-2026-52999 https://www.cve.org/CVERecord?id=CVE-2026-52999 Référence CVE CVE-2026-53001 https://www.cve.org/CVERecord?id=CVE-2026-53001 Référence CVE CVE-2026-53002 https://www.cve.org/CVERecord?id=CVE-2026-53002 Référence CVE CVE-2026-53003 https://www.cve.org/CVERecord?id=CVE-2026-53003 Référence CVE CVE-2026-53004 https://www.cve.org/CVERecord?id=CVE-2026-53004 Référence CVE CVE-2026-53006 https://www.cve.org/CVERecord?id=CVE-2026-53006 Référence CVE CVE-2026-53011 https://www.cve.org/CVERecord?id=CVE-2026-53011 Référence CVE CVE-2026-53012 https://www.cve.org/CVERecord?id=CVE-2026-53012 Référence CVE CVE-2026-53016 https://www.cve.org/CVERecord?id=CVE-2026-53016 Référence CVE CVE-2026-53021 https://www.cve.org/CVERecord?id=CVE-2026-53021 Référence CVE CVE-2026-53022 https://www.cve.org/CVERecord?id=CVE-2026-53022 Référence CVE CVE-2026-53023 https://www.cve.org/CVERecord?id=CVE-2026-53023 Référence CVE CVE-2026-53033 https://www.cve.org/CVERecord?id=CVE-2026-53033 Référence CVE CVE-2026-53034 https://www.cve.org/CVERecord?id=CVE-2026-53034 Référence CVE CVE-2026-53035 https://www.cve.org/CVERecord?id=

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。net/sched: taprioにおけるschedule切り替え時のadvance_sched()で発生していたuse-after-freeの問題を修正しました。advance_sched()内でshould_change_schedules()がtrueを返すと、管理スケジュールを運用スケジュールに昇格させるためにswitch_schedules()が呼び出されます。switch_schedules()は古い運用スケジュールをcall_rcu()を使ってRCU解放用にキューに入れますが、『next』はまだ古い運用スケジュールのエントリを指している状態です。その後の「next-＞end_time = end_time」や「rcu_assign_pointer(q-＞current_entry, next)」の処理がuse-after-freeとなっていました。これを修正するために、switch_schedules()の直後で新しい運用スケジュールから『next』を選択し、その事前計算済みのend_timeを使用するようにしました。setup_first_end_time()はスケジュールがインストールされる際に最初のエントリのend_timeをbase_time + intervalに設定するため、この値はすでに正しいものになっています。削除された「end_time = sched_base_time(admin)」の代入は別途問題を引き起こしていました。これは新しい最初のエントリの事前計算済みend_timeを単にbase_timeで上書きしてしまっていたためです。

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.2, 5.10.258 ≤ 5.10.*, 5.15.209 ≤ 5.15.*, 6.1.175 ≤ 6.1.*, 6.6.141 ≤ 6.6.*, 6.12.91 ≤ 6.12.*, 6.18.33 ≤ 6.18.*, 7.0.10 ≤ 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 24 Jun 2026 · Last source change 5 Aug 2026, 12:32 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-38879
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 ↗

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

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-38879↗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-53011 · cve.blacktree.nl