https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 07:47:24 +0000 https://vulnerability.circl.lu/vuln/cve-2022-50454 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/nouveau: fix a use-after-free in nouveau_gem_prime_import_sg_table()</p> <p>nouveau_bo_init() is backed by ttm_bo_init() and ferries its return code back to the caller. On failures, ttm will call nouveau_bo_del_ttm() and free the memory.Thus, when nouveau_bo_init() returns an error, the gem object has already been released. Then the call to nouveau_bo_ref() will use the freed &#34;nvbo-&gt;bo&#34; and lead to a use-after-free bug.</p> <p>We should delete the call to nouveau_bo_ref() to avoid the use-after-free.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/nouveau: fix a use-after-free in nouveau_gem_prime_import_sg_table()</p> <p>nouveau_bo_init() is backed by ttm_bo_init() and ferries its return code back to the caller. On failures, ttm will call nouveau_bo_del_ttm() and free the memory.Thus, when nouveau_bo_init() returns an error, the gem object has already been released. Then the call to nouveau_bo_ref() will use the freed &#34;nvbo-&gt;bo&#34; and lead to a use-after-free bug.</p> <p>We should delete the call to nouveau_bo_ref() to avoid the use-after-free.</p> https://vulnerability.circl.lu/vuln/cve-2022-50454