Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68780: sched/deadline: only set free_cpus for online runqueues

—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Fixed version: Linux Linux 382748c05e58a9f1935f5a653c352422375566ea, 3ed049fbfb4d75b4e0b8ab54c934f485129d5dc8, 9019e399684e3cc68c4a3f050e268f74d69c1317; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1.

Low priority for now. Upgrade to Linux Linux 382748c05e58a9f1935f5a653c352422375566ea, 3ed049fbfb4d75b4e0b8ab54c934f485129d5dc8, 9019e399684e3cc68c4a3f050e268f74d69c1317; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: sched/deadline: only set free_cpus for online runqueues Commit 16b269436b72 ("sched/deadline: Modify cpudl::free_cpus to reflect rd->online") introduced the cpudl_set/clear_freecpu functions to allow the cpu_dl::free_cpus mask to be manipulated by the deadline scheduler class rq_on/offline callbacks so the mask would also reflect this state. Commit 9659e1eeee28 ("sched/deadline: Remove cpu_active_mask from cpudl_find()") removed the check of the cpu_active_mask to save some processing on the premise that the cpudl::free_cpus mask already reflected the runqueue online state. Unfortunately, there are cases where it is possible for the cpudl_clear function to set the free_cpus bit for a CPU when the deadline runqueue is offline. When this occurs while a CPU is connected to the default root domain the flag may retain the bad state after the CPU has been unplugged. Later, a different CPU that is transitioning through the default root domain may push a deadline task to the powered down CPU when cpudl_find sees its free_cpus bit is set. If this happens the task will not have the opportunity to run. One example is outlined here: https://lore.kernel.org/lkml/20250110233010.2339521-1-opendmb@gmail.com Another occurs when the last deadline task is migrated from a CPU that has an offlined runqueue. The dequeue_task member of the deadline scheduler class will eventually call cpudl_clear and set the free_cpus bit for the CPU. This commit modifies the cpudl_clear function to be aware of the online state of the deadline runqueue so that the free_cpus mask can be updated appropriately. It is no longer necessary to manage the mask outside of the cpudl_set/clear functions so the cpudl_set/clear_freecpu functions are removed. In addition, since the free_cpus mask is now only updated under the cpudl lock the code was changed to use the non-atomic __cpumask functions.

Published
Jan 13, 2026
Updated
Jun 17, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-68780

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.0affected
    • 9659e1eeee28f7025b6545934d644d19e9c6e603 and later · before 9019e399684e3cc68c4a3f050e268f74d69c1317affected · git
    • 9659e1eeee28f7025b6545934d644d19e9c6e603 and later · before fb36846cbcc936954f2ad2bffdff13d16c0be08aaffected · git
    • 9659e1eeee28f7025b6545934d644d19e9c6e603 and later · before 91e448e69aca4bb0ba2e998eb3e555644db7322baffected · git
    • 9659e1eeee28f7025b6545934d644d19e9c6e603 and later · before dbc61834b0412435df21c71410562d933e4eba49affected · git
    • 9659e1eeee28f7025b6545934d644d19e9c6e603 and later · before 3ed049fbfb4d75b4e0b8ab54c934f485129d5dc8affected · git
    • 9659e1eeee28f7025b6545934d644d19e9c6e603 and later · before 382748c05e58a9f1935f5a653c352422375566eaaffected · git
    • before 4.0not affected · semver
    • 5.15.198 and later · up to and including 5.15.*not affected · semver
    • 6.1.160 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.18.3-16.18.3-1
openSUSE:Leap 16.0dtb-aarch64before 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-64kbbefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-azurebefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-defaultbefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-default-basebefore 6.12.0-160000.38.1.160000.2.226.12.0-160000.38.1.160000.2.22
openSUSE:Leap 16.0kernel-docsbefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-kvmsmallbefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-obs-buildbefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-obs-qabefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-rtbefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-sourcebefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-symsbefore 6.12.0-160000.38.16.12.0-160000.38.1
openSUSE:Leap 16.0kernel-zfcpdumpbefore 6.12.0-160000.38.16.12.0-160000.38.1
SUSE:Linux Enterprise Server 16.0kernel-azurebefore 6.12.0-160000.38.16.12.0-160000.38.1
SUSE:Linux Enterprise Server 16.0kernel-docsbefore 6.12.0-160000.38.16.12.0-160000.38.1
SUSE:Linux Enterprise Server 16.0kernel-kvmsmallbefore 6.12.0-160000.38.16.12.0-160000.38.1
SUSE:Linux Enterprise Server 16.0kernel-obs-qabefore 6.12.0-160000.38.16.12.0-160000.38.1
SUSE:Linux Enterprise Server 16.0kernel-zfcpdumpbefore 6.12.0-160000.38.16.12.0-160000.38.1
SUSE:Linux Micro 6.2kernel-64kbbefore 6.12.0-160000.38.16.12.0-160000.38.1
SUSE:Linux Micro 6.2kernel-defaultbefore 6.12.0-160000.38.16.12.0-160000.38.1
SUSE:Linux Micro 6.2kernel-default-basebefore 6.12.0-160000.38.1.160000.2.236.12.0-160000.38.1.160000.2.23

+4

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-68778Jan 13, 2026 · btrfs: don't log conflicting inode if it's a dir moved in the current transaction
    0Monitor
  • ← EarlierCVE-2025-68779Jan 13, 2026 · net/mlx5e: Avoid unregistering PSP twice
    0Monitor
  • Later →CVE-2025-68781Jan 13, 2026 · usb: phy: fsl-usb: Fix use-after-free in delayed work during device removal
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux382748c05e58a9f1935f5a653c352422375566eaVendor (CNA)
Linux Linux3ed049fbfb4d75b4e0b8ab54c934f485129d5dc8Vendor (CNA)
Linux Linux9019e399684e3cc68c4a3f050e268f74d69c1317Vendor (CNA)
Linux Linux91e448e69aca4bb0ba2e998eb3e555644db7322bVendor (CNA)
Linux Linuxdbc61834b0412435df21c71410562d933e4eba49Vendor (CNA)
Linux Linuxfb36846cbcc936954f2ad2bffdff13d16c0be08aVendor (CNA)
azl3 kernel 6.6.119.3-3 on Azure Linux 3.06.6.121.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-64kb6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-azure6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default-base6.12.0-160000.38.1.160000.2.22 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-docs6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-kvmsmall6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-build6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-qa6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-rt6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-source6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-syms6.12.0-160000.38.1 · openSUSE:Leap 16.0Package registry (OSV)
suse:kernel-64kb6.12.0-160000.38.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-azure6.12.0-160000.38.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-default6.12.0-160000.38.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-default-base6.12.0-160000.38.1.160000.2.23 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-docs6.12.0-160000.38.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-kvmsmall6.12.0-160000.38.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-obs-build6.12.0-160000.38.1 · SUSE:Linux Micro Extras 6.2Package registry (OSV)
suse:kernel-obs-qa6.12.0-160000.38.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-rt6.12.0-160000.38.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-source6.12.0-160000.38.1 · SUSE:Linux Micro 6.2Package registry (OSV)

+2

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records