https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 13:18:57 +0000 https://vulnerability.circl.lu/vuln/cve-2026-53011 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/sched: taprio: fix use-after-free in advance_sched() on schedule switch</p> <p>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 &#39;next&#39; still points into an entry of the old oper schedule. The subsequent &#39;next-&gt;end_time = end_time&#39; and rcu_assign_pointer(q-&gt;current_entry, next) are use-after-free.</p> <p>Fix this by selecting &#39;next&#39; from the new oper schedule immediately after switch_schedules(), and using its pre-calculated end_time. setup_first_end_time() sets the first entry&#39;s end_time to base_time + interval when the schedule is installed, so the value is already correct.</p> <p>The deleted &#39;end_time = sched_base_time(admin)&#39; assignment was also harmful independently: it would overwrite the new first entry&#39;s pre-calculated end_time with just base_time.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>net/sched: taprio: fix use-after-free in advance_sched() on schedule switch</p> <p>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 &#39;next&#39; still points into an entry of the old oper schedule. The subsequent &#39;next-&gt;end_time = end_time&#39; and rcu_assign_pointer(q-&gt;current_entry, next) are use-after-free.</p> <p>Fix this by selecting &#39;next&#39; from the new oper schedule immediately after switch_schedules(), and using its pre-calculated end_time. setup_first_end_time() sets the first entry&#39;s end_time to base_time + interval when the schedule is installed, so the value is already correct.</p> <p>The deleted &#39;end_time = sched_base_time(admin)&#39; assignment was also harmful independently: it would overwrite the new first entry&#39;s pre-calculated end_time with just base_time.</p> https://vulnerability.circl.lu/vuln/cve-2026-53011