Answer in brief
CVE-2026-53011 records a High severity (CVSS 7.8) vulnerability in net/sched: taprio: fix use-after-free in advance_sched() on schedule switch. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-53011 records a High severity (CVSS 7.8) vulnerability in net/sched: taprio: fix use-after-free in advance_sched() on schedule switch. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <a8fc396519ef4f081bc545e88f61241728bb78d7 || >=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <3471874578160a28c171a607fa069f24062634b8 || >=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <7256996e1ef553716817f3bfd077c2f3b48b582f || >=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <eee072fe16c646190d33ae69c9983d8de1562bf8 || >=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <1bd286fa3e21200133478ed523cc6a2788baf38a || >=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <b73235da5dde77ed1264f9767b62c28c9d71fd78 || >=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <0e62171df8ed4804d00db088f17eed06468233fa || >=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <105425b1969c5affe532713cfac1c0b320d7ac2b | a8fc396519ef4f081bc545e88f61241728bb78d7, 3471874578160a28c171a607fa069f24062634b8, 7256996e1ef553716817f3bfd077c2f3b48b582f, eee072fe16c646190d33ae69c9983d8de1562bf8, 1bd286fa3e21200133478ed523cc6a2788baf38a, b73235da5dde77ed1264f9767b62c28c9d71fd78, 0e62171df8ed4804d00db088f17eed06468233fa, 105425b1969c5affe532713cfac1c0b320d7ac2b |
| Linux/Linuxgeneric | 5.2 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <a8fc396519ef4f081bc545e88f61241728bb78d7 || >=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <3471874578160a28c171a607fa069f24062634b8 || >=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <7256996e1ef553716817f3bfd077c2f3b48b582f || >=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <eee072fe16c646190d33ae69c9983d8de1562bf8 || >=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <1bd286fa3e21200133478ed523cc6a2788baf38a || >=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <b73235da5dde77ed1264f9767b62c28c9d71fd78 || >=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <0e62171df8ed4804d00db088f17eed06468233fa || >=a3d43c0d56f1b94e74963a2fbadfb70126d92213 <105425b1969c5affe532713cfac1c0b320d7ac2b | a8fc396519ef4f081bc545e88f61241728bb78d7, 3471874578160a28c171a607fa069f24062634b8, 7256996e1ef553716817f3bfd077c2f3b48b582f, eee072fe16c646190d33ae69c9983d8de1562bf8, 1bd286fa3e21200133478ed523cc6a2788baf38a, b73235da5dde77ed1264f9767b62c28c9d71fd78, 0e62171df8ed4804d00db088f17eed06468233fa, 105425b1969c5affe532713cfac1c0b320d7ac2b |
| Linux/Linuxgeneric | 5.2 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.