CVE-2025-38522
Last modified
CVE-2025-38522 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: sched/ext: Prevent update_locked_rq() calls with NULL rq Avoid invoking update_locked_rq() when the runqueue (rq) pointer is NULL in the SCX_CALL_OP and SCX_CALL_OP_RET macros. Previously, calling update_locked_rq(NULL) with preemption enabled could trigger the following warning: BUG: using __this_cpu_write() in preemptible [00000000] This happens because __this_cpu_write() is unsafe to use in preemptible context. rq is NULL when an ops invoked from an unlocked context. In such cases, we don't need to store any rq, since the value should already be NULL (unlocked). EPSS estimates a 0.13% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: sched/ext: Prevent update_locked_rq() calls with NULL rq Avoid invoking update_locked_rq() when the runqueue (rq) pointer is NULL in the SCX_CALL_OP and SCX_CALL_OP_RET macros. Previously, calling update_locked_rq(NULL) with preemption enabled could trigger the following warning: BUG: using __this_cpu_write() in preemptible [00000000] This happens because __this_cpu_write() is unsafe to use in preemptible context. rq is NULL when an ops invoked from an unlocked context. In such cases, we don't need to store any rq, since the value should already be NULL (unlocked). Ensure that update_locked_rq() is only called when rq is non-NULL, preventing calling __this_cpu_write() on preemptible context.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.15.1, < 6.15.8 | — |
| Linux | Linux Kernel | 6.15 | — |
| Linux | Linux Kernel | 6.16 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-38522?
How severe is CVE-2025-38522?
How do I fix CVE-2025-38522?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-38517In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38518In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38519In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3852The WPshop 2 – E-Commerce plugin for WordPress is vulnerable…8.8
- CVE-2025-38520In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38521In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-38523In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38524In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-38525In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38526In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38527In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38528In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-38522?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST