In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG There were multiple issues in that code. First of all the order between the reset semaphore and the mm_lock was wrong (e.g. copy_to_user) was called while holding the lock. Then we allocated memory while holding the reset semaphore which is also a pretty big bug and can deadlock. Then we used down_read_trylock() instead of waiting for the reset to finish. (cherry picked from commit 361b6e6b303d4b691f6c5974d3eaab67ca6dd90e)

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG There were multiple issues in that code. First of all the order     between the reset semaphore and the mm_lock was wrong (e.g. copy_to_user) was called while holding the     lock. Then we allocated memory while holding the reset semaphore which is also a pretty big bug and can     deadlock. Then we used down_read_trylock() instead of waiting for the reset to finish. (cherry picked from     commit 361b6e6b303d4b691f6c5974d3eaab67ca6dd90e) (CVE-2026-53293)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Severity
329149	SUSE SLED15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2026:3166-1)	Nessus	SuSE Local Security Checks	medium
323753	Linux Distros Unpatched Vulnerability : CVE-2026-53293	Nessus	Misc.	medium

Detections

Analytics

CVE-2026-53293

medium

Tenable Plugins

medium

medium