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

sched/fair: Clear rel_deadline when initializing forked entities

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 13 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 severityMediumOperational priority:Low, lowered one band.downgradedsince 24 Jun 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.16% 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: No default targetRemediation target: Normal maintenance

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 13 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.

17 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 13 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 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.7.0.10-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-aws-6.14Affected, 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-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-azure-fde-6.14Affected, 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-nvidia-6.14Affected, 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-gcp-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-hwe-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-lowlatency-hwe-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-nvidia-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-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-oracle-6.14Affected, 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
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-52980 · CSAF 2.0 · revision 4 · interimSUSE Product Security TeamCVE-2026-52980
2 known affected

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

  • SUSE Linux Micro Extras 6.2:kernel-obs-build
  • SUSE Linux Micro Extras 6.2:kernel-syms
Summary
In the Linux kernel, the following vulnerability has been resolved: sched/fair: Clear rel_deadline when initializing forked entities A yield-triggered crash can happen when a newly forked sched_entity enters the fair class with se->rel_deadline unexpectedly set. The failing sequence is: 1. A task is forked while se->rel_deadline is still set. 2. __sched_fork() initializes vruntime, vlag and other sched_entity state, but does not clear rel_deadline. 3. On the first enqueue, enqueue_entity() calls place_entity(). 4. Because se->rel_deadline is set, place_entity() treats se->deadline as a relative deadline and converts it to an absolute deadline by adding the current vruntime. 5. However, the forked entity's deadline is not a valid inherited relative deadline for this new scheduling instance, so the conversion produces an abnormally large deadline. 6. If the task later calls sched_yield(), yield_task_fair() advances se->vruntime to se->deadline. 7. The inflated vruntime is then used by the following enqueue path, where the vruntime-derived key can overflow when multiplied by the entity weight. 8. This corrupts cfs_rq->sum_w_vruntime, breaks EEVDF eligibility calculation, and can eventually make all entities appear ineligible. pick_next_entity() may then return NULL unexpectedly, leading to a later NULL dereference. A captured trace shows the effect clearly. Before yield, the entity's vruntime was around: 9834017729983308 After yield_task_fair() executed: se->vruntime = se->deadline the vruntime jumped to: 19668035460670230 and the deadline was later advanced further to: 19668035463470230 This shows that the deadline had already become abnormally large before yield_task_fair() copied it into vruntime. rel_deadline is only meaningful when se->deadline really carries a relative deadline that still needs to be placed against vruntime. A freshly forked sched_entity should not inherit or retain this state. Clear se->rel_deadline in __sched_fork(), together with the other sched_entity runtime state, so that the first enqueue does not interpret the new entity's deadline as a stale relative deadline.
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-38848

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

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 13 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: sched/fair: Clear rel_deadline when initializing forked entities A yield-triggered crash can happen when a newly forked sched_entity enters the fair class with se->rel_deadline unexpectedly set. The failing sequence is: 1. A task is forked while se->rel_deadline is still set. 2. __sched_fork() initializes vruntime, vlag and other sched_entity state, but does not clear rel_deadline. 3. On the first enqueue, enqueue_entity() calls place_entity(). 4. Because se->rel_deadline is set, place_entity() treats se->deadline as a relative deadline and converts it to an absolute deadline by adding the current vruntime. 5. However, the forked entity's deadline is not a valid inherited relative deadline for this new scheduling instance, so the conversion produces an abnormally large deadline. 6. If the task later calls sched_yield(), yield_task_fair() advances se->vruntime to se->deadline. 7. The inflated vruntime is then used by the following enqueue path, where the vruntime-derived key can overflow when multiplied by the entity weight. 8. This corrupts cfs_rq->sum_w_vruntime, breaks EEVDF eligibility calculation, and can eventually make all entities appear ineligible. pick_next_entity() may then return NULL unexpectedly, leading to a later NULL dereference. A captured trace shows the effect clearly. Before yield, the entity's vruntime was around: 9834017729983308 After yield_task_fair() executed: se->vruntime = se->deadline the vruntime jumped to: 19668035460670230 and the deadline was later advanced further to: 19668035463470230 This shows that the deadline had already become abnormally large before yield_task_fair() copied it into vruntime. rel_deadline is only meaningful when se->deadline really carries a relative deadline that still needs to be placed against vruntime. A freshly forked sched_entity should not inherit or retain this state. Clear se->rel_deadline in __sched_fork(), together with the other sched_entity runtime state, so that the first enqueue does not interpret the new entity's deadline as a stale relative deadline.

What

In the Linux kernel, the following vulnerability has been resolved: sched/fair: Clear rel_deadline when initializing forked entities A yield-triggered crash can happen when a newly forked sched_entity enters the fair class with se->rel_deadline unexpectedly set. The failing sequence is: 1. A task is forked while se->rel_deadline is still set. 2. __sched_fork() initializes vruntime, vlag and other sched_entity state, but does not clear rel_deadline. 3. On the first enqueue, enqueue_entity() calls place_entity(). 4. Because se->rel_deadline is set, place_entity() treats se->deadline as a relative deadline and converts it to an absolute deadline by adding the current vruntime. 5. However, the forked entity's deadline is not a valid inherited relative deadline for this new scheduling instance, so the conversion produces an abnormally large deadline. 6. If the task later calls sched_yield(), yield_task_fair() advances se->vruntime to se->deadline. 7. The inflated vruntime is then used by the following enqueue path, where the vruntime-derived key can overflow when multiplied by the entity weight. 8. This corrupts cfs_rq->sum_w_vruntime, breaks EEVDF eligibility calculation, and can eventually make all entities appear ineligible. pick_next_entity() may then return NULL unexpectedly, leading to a later NULL dereference. A captured trace shows the effect clearly. Before yield, the entity's vruntime was around: 9834017729983308 After yield_task_fair() executed: se->vruntime = se->deadline the vruntime jumped to: 19668035460670230 and the deadline was later advanced further to: 19668035463470230 This shows that the deadline had already become abnormally large before yield_task_fair() copied it into vruntime. rel_deadline is only meaningful when se->deadline really carries a relative deadline that still needs to be placed against vruntime. A freshly forked sched_entity should not inherit or retain this state. Clear se->rel_deadline in __sched_fork(), together with the other sched_entity runtime state, so that the first enqueue does not interpret the new entity's deadline as a stale relative deadline.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: sched/fair: Clear rel_deadline when initializing forked entities A yield-triggered crash can happen when a newly forked sched_entity enters the fair class with se->rel_deadline unexpectedly set. The failing sequence is: 1. A task is forked while se->rel_deadline is still set. 2. __sched_fork() initializes vruntime, vlag and other sched_entity state, but does not clear rel_deadline. 3. On the first enqueue, enqueue_entity() calls place_entity(). 4. Because se->rel_deadline is set, place_entity() treats se->deadline as a relative deadline and converts it to an absolute deadline by adding the current vruntime. 5. However, the forked entity's deadline is not a valid inherited relative deadline for this new scheduling instance, so the conversion produces an abnormally large deadline. 6. If the task later calls sched_yield(), yield_task_fair() advances se->vruntime to se->deadline. 7. The inflated vruntime is then used by the following enqueue path, where the vruntime-derived key can overflow when multiplied by the entity weight. 8. This corrupts cfs_rq->sum_w_vruntime, breaks EEVDF eligibility calculation, and can eventually make all entities appear ineligible. pick_next_entity() may then return NULL unexpectedly, leading to a later NULL dereference. A captured trace shows the effect clearly. Before yield, the entity's vruntime was around: 9834017729983308 After yield_task_fair() executed: se->vruntime = se->deadline the vruntime jumped to: 19668035460670230 and the deadline was later advanced further to: 19668035463470230 This shows that the deadline had already become abnormally large before yield_task_fair() copied it into vruntime. rel_deadline is only meaningful when se->deadline really carries a relative deadline that still needs to be placed against vruntime. A freshly forked sched_entity should not inherit or retain this state. Clear se->rel_deadline in __sched_fork(), together with the other sched_entity runtime state, so that the first enqueue does not interpret the new entity's deadline as a stale relative deadline.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

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 → NULL Pointer Dereference → disrupt the affected service
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-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

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:N/I:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.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.
Denial of serviceCWE-476
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-52970 Référence CVE CVE-2026-52971 https://www.cve.org/CVERecord?id=CVE-2026-52971 Référence CVE CVE-2026-52973 https://www.cve.org/CVERecord?id=CVE-2026-52973 Référence CVE CVE-2026-52974 https://www.cve.org/CVERecord?id=CVE-2026-52974 Référence CVE CVE-2026-52975 https://www.cve.org/CVERecord?id=CVE-2026-52975 Référence CVE CVE-2026-52976 https://www.cve.org/CVERecord?id=CVE-2026-52976 Référence CVE CVE-2026-52977 https://www.cve.org/CVERecord?id=CVE-2026-52977 Référence CVE CVE-2026-52978 https://www.cve.org/CVERecord?id=CVE-2026-52978 Référence CVE CVE-2026-52979 https://www.cve.org/CVERecord?id=CVE-2026-52979 Référence CVE CVE-2026-52980 https://www.cve.org/CVERecord?id=CVE-2026-52980 Référence CVE CVE-2026-52981 https://www.cve.org/CVERecord?id=CVE-2026-52981 Référence CVE CVE-2026-52982 https://www.cve.org/CVERecord?id=CVE-2026-52982 Référence CVE CVE-2026-52983 https://www.cve.org/CVERecord?id=CVE-2026-52983 Référence CVE CVE-2026-52984 https://www.cve.org/CVERecord?id=CVE-2026-52984 Référence CVE CVE-2026-52985 https://www.cve.org/CVERecord?id=CVE-2026-52985 Référence CVE CVE-2026-52986 https://www.cve.org/CVERecord?id=CVE-2026-52986 Référence CVE CVE-2026-52987 https://www.cve.org/CVERecord?id=CVE-2026-52987 Référence CVE CVE-2026-52988 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-52970 Référence CVE CVE-2026-52971 https://www.cve.org/CVERecord?id=CVE-2026-52971 Référence CVE CVE-2026-52973 https://www.cve.org/CVERecord?id=CVE-2026-52973 Référence CVE CVE-2026-52974 https://www.cve.org/CVERecord?id=CVE-2026-52974 Référence CVE CVE-2026-52975 https://www.cve.org/CVERecord?id=CVE-2026-52975 Référence CVE CVE-2026-52976 https://www.cve.org/CVERecord?id=CVE-2026-52976 Référence CVE CVE-2026-52977 https://www.cve.org/CVERecord?id=CVE-2026-52977 Référence CVE CVE-2026-52978 https://www.cve.org/CVERecord?id=CVE-2026-52978 Référence CVE CVE-2026-52979 https://www.cve.org/CVERecord?id=CVE-2026-52979 Référence CVE CVE-2026-52980 https://www.cve.org/CVERecord?id=CVE-2026-52980 Référence CVE CVE-2026-52981 https://www.cve.org/CVERecord?id=CVE-2026-52981 Référence CVE CVE-2026-52982 https://www.cve.org/CVERecord?id=CVE-2026-52982 Référence CVE CVE-2026-52983 https://www.cve.org/CVERecord?id=CVE-2026-52983 Référence CVE CVE-2026-52984 https://www.cve.org/CVERecord?id=CVE-2026-52984 Référence CVE CVE-2026-52985 https://www.cve.org/CVERecord?id=CVE-2026-52985 Référence CVE CVE-2026-52986 https://www.cve.org/CVERecord?id=CVE-2026-52986 Référence CVE CVE-2026-52987 https://www.cve.org/CVERecord?id=CVE-2026-52987 Référence CVE CVE-2026-52988 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-52970 Référence CVE CVE-2026-52971 https://www.cve.org/CVERecord?id=CVE-2026-52971 Référence CVE CVE-2026-52973 https://www.cve.org/CVERecord?id=CVE-2026-52973 Référence CVE CVE-2026-52974 https://www.cve.org/CVERecord?id=CVE-2026-52974 Référence CVE CVE-2026-52975 https://www.cve.org/CVERecord?id=CVE-2026-52975 Référence CVE CVE-2026-52976 https://www.cve.org/CVERecord?id=CVE-2026-52976 Référence CVE CVE-2026-52977 https://www.cve.org/CVERecord?id=CVE-2026-52977 Référence CVE CVE-2026-52978 https://www.cve.org/CVERecord?id=CVE-2026-52978 Référence CVE CVE-2026-52979 https://www.cve.org/CVERecord?id=CVE-2026-52979 Référence CVE CVE-2026-52980 https://www.cve.org/CVERecord?id=CVE-2026-52980 Référence CVE CVE-2026-52981 https://www.cve.org/CVERecord?id=CVE-2026-52981 Référence CVE CVE-2026-52982 https://www.cve.org/CVERecord?id=CVE-2026-52982 Référence CVE CVE-2026-52983 https://www.cve.org/CVERecord?id=CVE-2026-52983 Référence CVE CVE-2026-52984 https://www.cve.org/CVERecord?id=CVE-2026-52984 Référence CVE CVE-2026-52985 https://www.cve.org/CVERecord?id=CVE-2026-52985 Référence CVE CVE-2026-52986 https://www.cve.org/CVERecord?id=CVE-2026-52986 Référence CVE CVE-2026-52987 https://www.cve.org/CVERecord?id=CVE-2026-52987 Référence CVE CVE-2026-52988 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-52970 Référence CVE CVE-2026-52971 https://www.cve.org/CVERecord?id=CVE-2026-52971 Référence CVE CVE-2026-52973 https://www.cve.org/CVERecord?id=CVE-2026-52973 Référence CVE CVE-2026-52974 https://www.cve.org/CVERecord?id=CVE-2026-52974 Référence CVE CVE-2026-52975 https://www.cve.org/CVERecord?id=CVE-2026-52975 Référence CVE CVE-2026-52976 https://www.cve.org/CVERecord?id=CVE-2026-52976 Référence CVE CVE-2026-52977 https://www.cve.org/CVERecord?id=CVE-2026-52977 Référence CVE CVE-2026-52978 https://www.cve.org/CVERecord?id=CVE-2026-52978 Référence CVE CVE-2026-52979 https://www.cve.org/CVERecord?id=CVE-2026-52979 Référence CVE CVE-2026-52980 https://www.cve.org/CVERecord?id=CVE-2026-52980 Référence CVE CVE-2026-52981 https://www.cve.org/CVERecord?id=CVE-2026-52981 Référence CVE CVE-2026-52982 https://www.cve.org/CVERecord?id=CVE-2026-52982 Référence CVE CVE-2026-52983 https://www.cve.org/CVERecord?id=CVE-2026-52983 Référence CVE CVE-2026-52984 https://www.cve.org/CVERecord?id=CVE-2026-52984 Référence CVE CVE-2026-52985 https://www.cve.org/CVERecord?id=CVE-2026-52985 Référence CVE CVE-2026-52986 https://www.cve.org/CVERecord?id=CVE-2026-52986 Référence CVE CVE-2026-52987 https://www.cve.org/CVERecord?id=CVE-2026-52987 Référence CVE CVE-2026-52988 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52943 Référence CVE CVE-2026-52954 https://www.cve.org/CVERecord?id=CVE-2026-52954 Référence CVE CVE-2026-52955 https://www.cve.org/CVERecord?id=CVE-2026-52955 Référence CVE CVE-2026-52956 https://www.cve.org/CVERecord?id=CVE-2026-52956 Référence CVE CVE-2026-52957 https://www.cve.org/CVERecord?id=CVE-2026-52957 Référence CVE CVE-2026-52958 https://www.cve.org/CVERecord?id=CVE-2026-52958 Référence CVE CVE-2026-52961 https://www.cve.org/CVERecord?id=CVE-2026-52961 Référence CVE CVE-2026-52962 https://www.cve.org/CVERecord?id=CVE-2026-52962 Référence CVE CVE-2026-52975 https://www.cve.org/CVERecord?id=CVE-2026-52975 Référence CVE CVE-2026-52980 https://www.cve.org/CVERecord?id=CVE-2026-52980 Référence CVE CVE-2026-52993 https://www.cve.org/CVERecord?id=CVE-2026-52993 Référence CVE CVE-2026-53015 https://www.cve.org/CVERecord?id=CVE-2026-53015 Référence CVE CVE-2026-53021 https://www.cve.org/CVERecord?id=CVE-2026-53021 Référence CVE CVE-2026-53035 https://www.cve.org/CVERecord?id=CVE-2026-53035 Référence CVE CVE-2026-53036 https://www.cve.org/CVERecord?id=CVE-2026-53036 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=CVE-2026-53040 Référence CVE CVE-2026-53041 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-52970 Référence CVE CVE-2026-52971 https://www.cve.org/CVERecord?id=CVE-2026-52971 Référence CVE CVE-2026-52973 https://www.cve.org/CVERecord?id=CVE-2026-52973 Référence CVE CVE-2026-52974 https://www.cve.org/CVERecord?id=CVE-2026-52974 Référence CVE CVE-2026-52975 https://www.cve.org/CVERecord?id=CVE-2026-52975 Référence CVE CVE-2026-52976 https://www.cve.org/CVERecord?id=CVE-2026-52976 Référence CVE CVE-2026-52977 https://www.cve.org/CVERecord?id=CVE-2026-52977 Référence CVE CVE-2026-52978 https://www.cve.org/CVERecord?id=CVE-2026-52978 Référence CVE CVE-2026-52979 https://www.cve.org/CVERecord?id=CVE-2026-52979 Référence CVE CVE-2026-52980 https://www.cve.org/CVERecord?id=CVE-2026-52980 Référence CVE CVE-2026-52981 https://www.cve.org/CVERecord?id=CVE-2026-52981 Référence CVE CVE-2026-52982 https://www.cve.org/CVERecord?id=CVE-2026-52982 Référence CVE CVE-2026-52983 https://www.cve.org/CVERecord?id=CVE-2026-52983 Référence CVE CVE-2026-52984 https://www.cve.org/CVERecord?id=CVE-2026-52984 Référence CVE CVE-2026-52985 https://www.cve.org/CVERecord?id=CVE-2026-52985 Référence CVE CVE-2026-52986 https://www.cve.org/CVERecord?id=CVE-2026-52986 Référence CVE CVE-2026-52987 https://www.cve.org/CVERecord?id=CVE-2026-52987 Référence CVE CVE-2026-52988 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-52958 Référence CVE CVE-2026-52961 https://www.cve.org/CVERecord?id=CVE-2026-52961 Référence CVE CVE-2026-52962 https://www.cve.org/CVERecord?id=CVE-2026-52962 Référence CVE CVE-2026-52963 https://www.cve.org/CVERecord?id=CVE-2026-52963 Référence CVE CVE-2026-52964 https://www.cve.org/CVERecord?id=CVE-2026-52964 Référence CVE CVE-2026-52969 https://www.cve.org/CVERecord?id=CVE-2026-52969 Référence CVE CVE-2026-52972 https://www.cve.org/CVERecord?id=CVE-2026-52972 Référence CVE CVE-2026-52975 https://www.cve.org/CVERecord?id=CVE-2026-52975 Référence CVE CVE-2026-52976 https://www.cve.org/CVERecord?id=CVE-2026-52976 Référence CVE CVE-2026-52980 https://www.cve.org/CVERecord?id=CVE-2026-52980 Référence CVE CVE-2026-52981 https://www.cve.org/CVERecord?id=CVE-2026-52981 Référence CVE CVE-2026-52982 https://www.cve.org/CVERecord?id=CVE-2026-52982 Référence CVE CVE-2026-52989 https://www.cve.org/CVERecord?id=CVE-2026-52989 Référence CVE CVE-2026-52993 https://www.cve.org/CVERecord?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-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-53009 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-52970 Référence CVE CVE-2026-52971 https://www.cve.org/CVERecord?id=CVE-2026-52971 Référence CVE CVE-2026-52973 https://www.cve.org/CVERecord?id=CVE-2026-52973 Référence CVE CVE-2026-52974 https://www.cve.org/CVERecord?id=CVE-2026-52974 Référence CVE CVE-2026-52975 https://www.cve.org/CVERecord?id=CVE-2026-52975 Référence CVE CVE-2026-52976 https://www.cve.org/CVERecord?id=CVE-2026-52976 Référence CVE CVE-2026-52977 https://www.cve.org/CVERecord?id=CVE-2026-52977 Référence CVE CVE-2026-52978 https://www.cve.org/CVERecord?id=CVE-2026-52978 Référence CVE CVE-2026-52979 https://www.cve.org/CVERecord?id=CVE-2026-52979 Référence CVE CVE-2026-52980 https://www.cve.org/CVERecord?id=CVE-2026-52980 Référence CVE CVE-2026-52981 https://www.cve.org/CVERecord?id=CVE-2026-52981 Référence CVE CVE-2026-52982 https://www.cve.org/CVERecord?id=CVE-2026-52982 Référence CVE CVE-2026-52983 https://www.cve.org/CVERecord?id=CVE-2026-52983 Référence CVE CVE-2026-52984 https://www.cve.org/CVERecord?id=CVE-2026-52984 Référence CVE CVE-2026-52985 https://www.cve.org/CVERecord?id=CVE-2026-52985 Référence CVE CVE-2026-52986 https://www.cve.org/CVERecord?id=CVE-2026-52986 Référence CVE CVE-2026-52987 https://www.cve.org/CVERecord?id=CVE-2026-52987 Référence CVE CVE-2026-52988 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-023767LinuxのLinux KernelにおけるNULL ポインタデリファレンスに関する脆弱性

Linuxカーネルにおいて、以下の脆弱性が修正されました。sched/fairにて、フォークされたエンティティの初期化時にrel_deadlineをクリアしないために、新たにフォークされたsched_entityが予期せずse-＞rel_deadlineが設定されたままfairクラスに入ることで、yieldをトリガーとするクラッシュが発生する可能性があります。問題のあるシーケンスは以下の通りです。 1. se-＞rel_deadlineがまだ設定されたままタスクがフォークされる。 2. __sched_fork()がvruntime、vflagおよび他のsched_entity状態を初期化するが、rel_deadlineはクリアしない。 3. 最初のenqueue時にenqueue_entity()がplace_entity()を呼び出す。 4. se-＞rel_deadlineが設定されているため、place_entity()はse-＞deadlineを相対デッドラインとみなし、現在のvruntimeを加算して絶対デッドラインに変換する。 5. しかし、フォークされたエンティティのデッドラインはこの新しいスケジューリングインスタンスに対して有効な継承された相対デッドラインではないため、変換によって異常に大きなデッドラインが生成される。 6. その後タスクがsched_yield()を呼ぶと、yield_task_fair()はse-＞vruntimeをse-＞deadlineまで進める。 7. その膨張したvruntimeは次のenqueue時に使用され、vruntimeから派生したキーがエンティティの重みと乗算される際にオーバーフローを引き起こす可能性がある。 8. これによりcfs_rq-＞sum_w_vruntimeが破損し、EEVDFの適格判定が壊れて最終的にすべてのエンティティが不適格として扱われるようになります。その結果、pick_next_entity()が予期せずNULLを返し、後続のNULL参照につながる可能性があります。トレースデータはこの影響を明確に示しています。yield前のエンティティのvruntimeは約9,834,017,729,983,308でしたが、yield_task_fair()実行後（se-＞vruntime = se-＞deadline）にはvruntimeが19,668,035,460,670,230まで跳ね上がり、その後デッドラインはさらに19,668,035,463,470,230まで進められました。これは、deadlineがyield_task_fair()がvruntimeにコピーする前からすでに異常に大きくなっていたことを示しています。rel_deadlineは、se-＞deadlineがまだvruntimeに対して相対的なデッドラインを持ち、それを用いて位置付ける必要がある場合にのみ意味を持ちます。新たにフォークされたsched_entityは、この状態を継承または保持してはなりません。したがって、__sched_fork()内でse-＞rel_deadlineを他のsched_entityランタイム状態とともにクリアし、最初のenqueue時に新しいエンティティのデッドラインが古い相対デッドラインとして誤って解釈されないように対策しました。

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: < 6.12, 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 24 Jun 2026, 16:28 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
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-38848
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-38848↗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-52980 · cve.blacktree.nl