NULL Pointer Dereference The advisory has been revoked - it doesn't affect any version of package kernel-64k-debug-devel-matched (opens in a new tab)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RHEL9-KERNEL64KDEBUGDEVELMATCHED-10734706
- published14 Jul 2025
- disclosed2 May 2025
Introduced: 2 May 2025
CVE-2023-53095 (opens in a new tab)Amendment
The Red Hat security team deemed this advisory irrelevant for RHEL:9.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-64k-debug-devel-matched package and not the kernel-64k-debug-devel-matched package as distributed by RHEL.
In the Linux kernel, the following vulnerability has been resolved:
drm/ttm: Fix a NULL pointer dereference
The LRU mechanism may look up a resource in the process of being removed from an object. The locking rules here are a bit unclear but it looks currently like res->bo assignment is protected by the LRU lock, whereas bo->resource is protected by the object lock, while clearing of bo->resource is also protected by the LRU lock. This means that if we check that bo->resource points to the LRU resource under the LRU lock we should be safe. So perform that check before deciding to swap out a bo. That avoids dereferencing a NULL bo->resource in ttm_bo_swapout().