Bug 2373366 (CVE-2025-38012) - CVE-2025-38012 kernel: sched_ext: bpf_iter_scx_dsq_new() should always initialize iterator
Summary: CVE-2025-38012 kernel: sched_ext: bpf_iter_scx_dsq_new() should always initia...
Keywords:
Status: NEW
Alias: CVE-2025-38012
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-06-18 10:03 UTC by OSIDB Bzimport
Modified: 2025-06-20 17:54 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-06-18 10:03:52 UTC
In the Linux kernel, the following vulnerability has been resolved:

sched_ext: bpf_iter_scx_dsq_new() should always initialize iterator

BPF programs may call next() and destroy() on BPF iterators even after new()
returns an error value (e.g. bpf_for_each() macro ignores error returns from
new()). bpf_iter_scx_dsq_new() could leave the iterator in an uninitialized
state after an error return causing bpf_iter_scx_dsq_next() to dereference
garbage data. Make bpf_iter_scx_dsq_new() always clear $kit->dsq so that
next() and destroy() become noops.

Comment 1 Avinash Hanwate 2025-06-20 17:45:28 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025061843-CVE-2025-38012-6d55@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.