References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to nvd@nist.gov.

Known Affected Software Configurations Switch to CPE 2.2

Change History

OR
     *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions up to (excluding) 6.10.5

NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

NIST CWE-667

https://git.kernel.org/stable/c/3cd1585e57908b6efcd967465ef7685f40b2a294 No Types Assigned

https://git.kernel.org/stable/c/3cd1585e57908b6efcd967465ef7685f40b2a294 Patch

https://git.kernel.org/stable/c/458bb83119dfee5d14c677f7846dd9363817006f No Types Assigned

https://git.kernel.org/stable/c/458bb83119dfee5d14c677f7846dd9363817006f Patch

In the Linux kernel, the following vulnerability has been resolved:

drm/xe/preempt_fence: enlarge the fence critical section

It is really easy to introduce subtle deadlocks in
preempt_fence_work_func() since we operate on single global ordered-wq
for signalling our preempt fences behind the scenes, so even though we
signal a particular fence, everything in the callback should be in the
fence critical section, since blocking in the callback will prevent
other published fences from signalling. I

kernel.org https://git.kernel.org/stable/c/3cd1585e57908b6efcd967465ef7685f40b2a294 [No types assigned]

kernel.org https://git.kernel.org/stable/c/458bb83119dfee5d14c677f7846dd9363817006f [No types assigned]