CyberRota Analysis
AI-GeneratedThe vulnerability in the Linux kernel affects the error handling in the `rocket_job_run()` function, leading to a reference leak of the `done_fence` and improper management of the runtime PM reference, which can prevent the NPU from suspending. Additionally, it risks returning an unsignaled fence to the DRM scheduler, potentially causing system warnings. Linux system administrators and developers working with the affected kernel should prioritize addressing this issue to ensure proper resource management and system stability.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: accel/rocket: Fix error path handling in rocket_job_run() In rocket_job_run(), after taking an extra fence reference for job->done_fence via dma_fence_get(), the error paths have three bugs: - The dma_fence reference held by job->done_fence is never released, causing a reference leak. - pm_runtime_get_sync() increments the usage counter even on failure, but the error path does not decrement it, leaking the runtime PM reference and preventing the NPU from suspending. - A valid but unsignaled fence is returned to the DRM scheduler, which triggers WARN("Fence ... released with pending signals!") when the scheduler drops its reference. Fix by replacing pm_runtime_get_sync() with pm_runtime_resume_and_get() which auto-balances the usage counter on failure, releasing both fence references on error, and returning ERR_PTR(ret) instead of the unsignaled fence. [tomeu: Refactored error paths to use consolidated goto labels]