Skip to content
VulniPulse
Advisory severityHigh7.0Vendor: MediumRed Hat Linux

High [CVE-2026-53011] fix use-after-free in advance_sched on schedule switch

This high-severity Red Hat Linux advisory covers CVE-2026-53011 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 9, Shadow Migration Toolkit for Virtualization for RHEL 10.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-53011 Source published Source updated

VulniPulse record published Record updated

CVE-2026-53011
Affected products & platforms
Red Hat LinuxLinux Kernel
Open source advisory

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. A flaw was found in the Linux kernel's networking scheduler, specifically within the `taprio` module.

When the system attempts to switch schedules, a use-after-free vulnerability occurs in the `advance_sched()` function. This happens because a pointer to an old schedule entry is still used after the memory for that entry has been queued for release.

Is CVE-2026-53011 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-53011 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-53011?

Upgrade to a fixed release named by Red Hat:

  • kernel-0:6.12.0-211.66.1.el10_2
  • kernel-0:5.14.0-687.58.1.el9_8
  • RHSA-2026:83207
  • RHSA-2026:83156

Confirm against the vendor advisory before you patch.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Fixed versions
  • kernel-0:6.12.0-211.66.1.el10_2
  • kernel-0:5.14.0-687.58.1.el9_8
  • RHSA-2026:83207
  • RHSA-2026:83156

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Mitigation

Upgrade to a fixed release: kernel-0:6.12.0-211.66.1.el10_2, kernel-0:5.14.0-687.58.1.el9_8, RHSA-2026:83207, RHSA-2026:83156. That is the remediation for this advisory.

The vendor advisory may list interim mitigations or workarounds not captured here. Review it before change work.

Official advisory · high-confidence parse· fetched 14 days ago·verify at source

Get an email when Red Hat Linux Kernel publishes the next one.

See Red Hat Linux Kernel's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat Linux Kernel
All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.