CVE-2026-68094 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, as well as users of the Linux kernel, should be aware of this vulnerability and take steps to ensure their systems are updated with the fix.

Technical summary

The Linux kernel's sched_ext component has a vulnerability that can cause a lockdep assertion when restoring an rq that is no longer held. The issue arises from the improper preservation of rq tracking across local DSQ dispatch. The problem occurs when dispatch_to_local_dsq() runs from scx_bpf_dsq_move_to_local() while ops.dispatch() has recorded the current rq. This can cause a lock switch, triggering a lockdep assertion. The vulnerability has been resolved with the introduction of switch_rq_lock() to update the tracking state together with each rq lock handoff.

Defensive priority

Medium

Recommended defensive actions

• Review and apply the provided patches to ensure the Linux kernel is updated with the fix.
• Monitor the Linux kernel's sched_ext component for any potential issues or updates.
• Perform regular vulnerability assessments and penetration testing to identify potential vulnerabilities.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and NVD entry provide information on the vulnerability. However, the details are limited, and further analysis is required to fully understand the issue. The Linux kernel's sched_ext component is affected, and the vulnerability has been resolved with the introduction of switch_rq_lock() to update the tracking state together with each rq lock handoff.

Official resources