high CVSS 7.8

CVE-2024-46820·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vcn: remove irq disabling in vcn 5 suspend We do not directly enable/disable VCN IRQ in vcn 5.0.0. And we do not handle the IRQ state as well. So the calls to disable IRQ and set state are removed. This effectively gets rid of the warining of "WARN_ON(!amdgpu_irq_enabled(adev, src, type))" in amdgpu_irq_put().

Severity
high
Software
Kernel
Fixed in
6.10.9
Published
2024-09-27

Affected versions

From: 6.10

Until: 6.10.9

Fixed in: 6.10.9

How to fix this CVE

Update your Linux kernel to version 6.10.9 or later to resolve this VCN 5 IRQ state management issue. The vulnerability stems from improper IRQ disabling logic in the AMD GPU video codec engine that triggers kernel warnings and potential instability. Systems running kernel versions 6.10 through 6.10.8 should prioritize this patch to maintain system stability and avoid spurious IRQ warnings during suspend operations.

sudo dnf update kernel kernel-devel

Defensia detects this vulnerability

How to check if you are affected

  1. Check kernel version: uname -r — verify if version is between 6.10 and 6.10.8 (vulnerable range)
  2. Confirm VCN 5 hardware: lspci | grep -i 'video codec engine' or check dmesg | grep -i 'vcn 5' for VCN initialization messages
  3. Review kernel logs for IRQ warnings: dmesg | grep -i 'WARN_ON.*amdgpu_irq' or journalctl -b | grep 'amdgpu_irq_put'
  4. Verify patch applied: grep -r 'remove irq disabling in vcn 5 suspend' /boot/config-$(uname -r) or compare kernel build date against the fix date (after CVE publication)

FAQ

What is CVE-2024-46820?

This CVE addresses a bug in the AMD GPU VCN 5 driver where the kernel incorrectly attempts to disable IRQs during suspend operations that were never directly enabled, causing spurious kernel warnings and potential system stability issues.

Is CVE-2024-46820 being actively exploited?

No, there are no known active exploits or public proof-of-concept code for this vulnerability. It is not listed on the CISA Known Exploited Vulnerabilities catalog.

What versions of Kernel are affected by CVE-2024-46820?

Linux kernel versions 6.10 through 6.10.8 are affected. The vulnerability is patched in kernel 6.10.9 and later.

How do I check if my server is vulnerable to CVE-2024-46820?

Run 'uname -r' and verify your kernel version. If it reports 6.10 through 6.10.8 and your system has AMD GPU with VCN 5 (check 'lspci | grep -i amd'), you are vulnerable. Check dmesg for 'WARN_ON.*amdgpu_irq' warnings.

Does Defensia detect CVE-2024-46820?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2024-46820 will appear in your dashboard with remediation steps.

Related Kernel CVEs

CVE-2026-100075CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: RDMA/srpt: Fix srpt_alloc_rw_ctxs() unwind counters When srpt_alloc_rw_ctxs() fails partway through a multi-buffer indirect descriptor, the unwind path destroys RDMA contexts but leaves stale n_rw_ctx and n_rdma values (and a dangling rw_ctxs pointer). Later sq_wr_avail accounting in srpt_queue_response() or srpt_write_pending() can then subtract the wrong number of send queue credits. Reset the counters and clear rw_ctxs after freeing the heap allocation before returning an error.
CVE-2026-64035CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: igc: set tx buffer type for SMD frames Sashiko pointed out that igc_fpe_init_smd_frame() initializes igc_tx_buffer fields for an SMD skb, but does not set the buffer type: https://sashiko.dev/#/patchset/20260415025226.114115-1-kohei%40enjuk.jp Since igc_tx_buffer entries are reused, a stale XDP or XSK type can remain and make TX completion use the wrong cleanup path. Set the buffer type to IGC_TX_BUFFER_TYPE_SKB.
CVE-2026-64033CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs: Fix use-after-free in path file creation cleanup In the error path of rtrs_srv_create_path_files(), the sysfs root folders may already have been created and srv_path->kobj may already have been initialized. If a later step fails, the cleanup currently calls kobject_put(&srv_path->kobj) before rtrs_srv_destroy_once_sysfs_root_folders(srv_path). kobject_put() may drop the last reference to srv_path->kobj and invoke the release callback, rtrs_srv_release(), which frees srv_path. The following call to rtrs_srv_destroy_once_sysfs_root_folders(srv_path) then dereferences srv_path internally to access srv_path->srv, resulting in a use-after-free. This failure path is reached before rtrs_srv_create_path_files() returns success, so the successful-path lifetime handling is not involved. Fix this by destroying the sysfs root folders before calling kobject_put(&srv_path->kobj), so srv_path is still valid while the helper accesses it. This issue was found by a static analysis tool I am developing.
CVE-2026-64037CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mld: fix TSO segmentation explosion when AMSDU is disabled When the TLC notification disables AMSDU for a TID, the MLD driver sets max_tid_amsdu_len to the sentinel value 1. The TSO segmentation path in iwl_mld_tx_tso_segment() checks for zero but not for this sentinel, allowing it to reach the num_subframes calculation: num_subframes = (max_tid_amsdu_len + pad) / (subf_len + pad) = (1 + 2) / (1534 + 2) = 0 This zero propagates to iwl_tx_tso_segment() which sets: gso_size = num_subframes * mss = 0 Calling skb_gso_segment() with gso_size=0 creates over 32000 tiny segments from a single GSO skb. This floods the TX ring with ~1024 micro-frames (the rest are purged), creating a massive burst of TX completion events that can lead to memory corruption and a subsequent use-after-free in TCP's retransmit queue (refcount underflow in tcp_shifted_skb, NULL deref in tcp_rack_detect_loss). The MVM driver is immune because it checks mvmsta->amsdu_enabled before reaching the num_subframes calculation. The MLD driver has no equivalent bitmap check and relies solely on max_tid_amsdu_len, which does not catch the sentinel value. Fix this by detecting the sentinel value (max_tid_amsdu_len == 1) at the existing check and falling back to non-AMSDU TSO segmentation. Also add a WARN_ON_ONCE guard after the num_subframes division as defense-in-depth to catch any future code paths that produce zero through a different mechanism.
CVE-2026-64000CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: net: hsr: fix potential OOB access in supervision frame handling Ensure the entire TLV header is linearized before access by adding sizeof(struct hsr_sup_tlv) to the pskb_may_pull() calls. Without this, a truncated frame could cause an out-of-bounds access.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-46820. Free for 1 server.

Get started free