Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.

Threats Tagged 'cve-2026-53293'

View all threats tagged with 'cve-2026-53293'. Filter and sort to focus on specific types of threats.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Tag: cve-2026-53293

Threats Tagged 'cve-2026-53293'

Click on any threat for detailed analysis and mitigation recommendations

Linux hwe edge: 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. (CVE-2026-53293)CVE-2026-53293
0

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)

Join the discussion
A vulnerability in the Linux kernel's AMDGPU driver related to the AMDGPU_INFO_READ_MMR_REG functionality was resolved. (CVE-2026-53293)CVE-2026-53293
0

A vulnerability in the Linux kernel's AMDGPU driver related to the AMDGPU_INFO_READ_MMR_REG functionality was resolved. The issues included incorrect locking order, memory allocation while holding a semaphore leading to potential deadlocks, and improper use of down_read_trylock instead of waiting for reset completion. These flaws could cause denial of service due to deadlocks or hangs.

Join the discussion

Showing 1 to 2 of 2 results

Filters:Tag: cve-2026-53293
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses