Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-45919: sched/rt: Skip currently executing CPU in rto_next_cpu()

Noroxi assessment

Priority: Monitor (action score 22/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.13% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 16ca9f3117e9a294646c897daf08a5ab546c711b, 3b3c672a66db3de3b40f8a7057864bc1f874ede3, 4.10.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 16ca9f3117e9a294646c897daf08a5ab546c711b, 3b3c672a66db3de3b40f8a7057864bc1f874ede3, 4.10 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/rt: Skip currently executing CPU in rto_next_cpu() CPU0 becomes overloaded when hosting a CPU-bound RT task, a non-CPU-bound RT task, and a CFS task stuck in kernel space. When other CPUs switch from RT to non-RT tasks, RT load balancing (LB) is triggered; with HAVE_RT_PUSH_IPI enabled, they send IPIs to CPU0 to drive the execution of rto_push_irq_work_func. During push_rt_task on CPU0, if next_task->prio < rq->donor->prio, resched_curr() sets NEED_RESCHED and after the push operation completes, CPU0 calls rto_next_cpu(). Since only CPU0 is overloaded in this scenario, rto_next_cpu() should ideally return -1 (no further IPI needed). However, multiple CPUs invoking tell_cpu_to_push() during LB increments rd->rto_loop_next. Even when rd->rto_cpu is set to -1, the mismatch between rd->rto_loop and rd->rto_loop_next forces rto_next_cpu() to restart its search from -1. With CPU0 remaining overloaded (satisfying rt_nr_migratory && rt_nr_total > 1), it gets reselected, causing CPU0 to queue irq_work to itself and send self-IPIs repeatedly. As long as CPU0 stays overloaded and other CPUs run pull_rt_tasks(), it falls into an infinite self-IPI loop, which triggers a CPU hardlockup due to continuous self-interrupts. The trigging scenario is as follows: cpu0 cpu1 cpu2 pull_rt_task tell_cpu_to_push <------------irq_work_queue_on rto_push_irq_work_func push_rt_task resched_curr(rq) pull_rt_task rto_next_cpu tell_cpu_to_push <-------------------------- atomic_inc(rto_loop_next) rd->rto_loop != next rto_next_cpu irq_work_queue_on rto_push_irq_work_func Fix redundant self-IPI by filtering the initiating CPU in rto_next_cpu(). This solution has been verified to effectively eliminate spurious self-IPIs and prevent CPU hardlockup scenarios.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 27, 2026
Updated
Jun 24, 2026
EPSS
0.1% · 2th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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-2026-45919

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

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack 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 (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

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

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.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel4.4.103 and later · before 4.5
  • linux linux kernel4.9.66 and later · before 4.10
  • linux linux kernel4.14.3 and later · before 5.10.252
  • linux linux kernel5.11 and later · before 5.15.202
  • linux linux kernel5.16 and later · before 6.1.165
  • linux linux kernel6.2 and later · before 6.6.128
  • linux linux kernel6.7 and later · before 6.12.75
  • linux linux kernel6.13 and later · before 6.18.14
  • linux linux kernel6.19 and later · before 6.19.4

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

    • cb1831a83e54cd3269a2420fce81c4fd8ae6f667, 1c37ff78298a6b6063649123356a312e1cce12ca, f17c786b28a3060a566a170c2cf3bd7441fc30a3, 4.15affected
    • 4bdced5c9a2922521e325896a7bbbf0132c94e56 and later · before d57d0746276a88ea43a2cc62b849fd8a95e32e41affected · git
    • 4bdced5c9a2922521e325896a7bbbf0132c94e56 and later · before 3b3c672a66db3de3b40f8a7057864bc1f874ede3affected · git
    • 4bdced5c9a2922521e325896a7bbbf0132c94e56 and later · before 16ca9f3117e9a294646c897daf08a5ab546c711baffected · git
    • 4bdced5c9a2922521e325896a7bbbf0132c94e56 and later · before 8ad5577b2d4acfd83f03d97a0aece2d18aac5f07affected · git
    • 4bdced5c9a2922521e325896a7bbbf0132c94e56 and later · before a6a73403733e86748421f2eeaf028c85683ef896affected · git
    • 4bdced5c9a2922521e325896a7bbbf0132c94e56 and later · before 52aeb1e07ec223caf212f036817976c98d2aa250affected · git
    • 4bdced5c9a2922521e325896a7bbbf0132c94e56 and later · before 9f25edc5a20cb52a5abbf25f0724bb4732b81801affected · git
    • 4bdced5c9a2922521e325896a7bbbf0132c94e56 and later · before 94894c9c477e53bcea052e075c53f89df3d2a33eaffected · git
    • 4.4.103 and later · before 4.5affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:9kernelbefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-64kbefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-64k-corebefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-64k-debugbefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-64k-develbefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-corebefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-cross-headersbefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-debugbefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-debug-corebefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-debug-develbefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8
AlmaLinux:9kernel-debug-modules-corebefore 5.14.0-687.56.1.el9_85.14.0-687.56.1.el9_8

+53

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-45916May 27, 2026 · power: supply: sbs-battery: Fix use-after-free in power_supply_changed()
    31Monitor
  • ← EarlierCVE-2026-45918May 27, 2026 · ovpn: tcp - don't deref NULL sk_socket member after tcp_close()
    22Monitor
  • Later →CVE-2026-45920May 27, 2026 · ext4: fix dirtyclusters double decrement on fs shutdown
    31Monitor

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 Linux16ca9f3117e9a294646c897daf08a5ab546c711bVendor (CNA)
Linux Linux3b3c672a66db3de3b40f8a7057864bc1f874ede3Vendor (CNA)
Linux Linux4.10Vendor (CNA)
Linux Linux4.15Vendor (CNA)
Linux Linux4.5Vendor (CNA)
Linux Linux52aeb1e07ec223caf212f036817976c98d2aa250Vendor (CNA)
Linux Linux8ad5577b2d4acfd83f03d97a0aece2d18aac5f07Vendor (CNA)
Linux Linux94894c9c477e53bcea052e075c53f89df3d2a33eVendor (CNA)
Linux Linux9f25edc5a20cb52a5abbf25f0724bb4732b81801Vendor (CNA)
Linux Linuxa6a73403733e86748421f2eeaf028c85683ef896Vendor (CNA)
Linux Linuxd57d0746276a88ea43a2cc62b849fd8a95e32e41Vendor (CNA)
almalinux:kernel5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.56.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.170-1 · Debian:12Package registry (OSV)

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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-3144835 days apartext4: avoid infinite loops caused by residual data
    37Monitor
  • CVE-2026-6388953 days apartscsi: scsi_transport_fc: Widen FPIN pname walker counter to u32
    32Monitor
  • CVE-2026-5293328 days apartio_uring/poll: fix signed comparison in io_poll_get_ownership()
    31Monitor
  • CVE-2026-460520 days apartceph: only d_add() negative dentries when they are unhashed
    30Monitor
  • CVE-2026-3155233 days apartwifi: wlcore: Return -ENOMEM instead of -EAGAIN if there is not enough headroom
    30Monitor
  • CVE-2026-6414853 days apartpds_core: fix error handling in pdsc_devcmd_wait
    30Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

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.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records