Skip to main content
VulnerabilityPublished Updated

CVE-2026-45853: Linux kernel · drm/amdgpu: Use kvfree instead of kfree in amdgpu_gmc_get_nps_memranges()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f441538893eba6347b983f2904819ca6c99da65e : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in f441538893eba6347b983f2904819ca6c99da65e, 16e7e7ad8cdc6b4c4af7f31e262f1494c1b2a55e, 9ae85b0c1909b6c6bfd2636b04cdaf7f520bf2b5 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade Linux kernel to f441538893eba6347b983f2904819ca6c99da65e, 16e7e7ad8cdc6b4c4af7f31e262f1494c1b2a55e, 9ae85b0c1909b6c6bfd2636b04cdaf7f520bf2b5 or 0c44d61945c4a80775292d96460aa2f22e62f86c.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ b194d21b9bcc15b50df1bc3ff7428e51c2918a6f, < f441538893eba6347b983f2904819ca6c99da65e
Fixed in
  • f441538893eba6347b983f2904819ca6c99da65e
LinuxLinuxAffected
  • ≥ b194d21b9bcc15b50df1bc3ff7428e51c2918a6f, < 16e7e7ad8cdc6b4c4af7f31e262f1494c1b2a55e
Fixed in
  • 16e7e7ad8cdc6b4c4af7f31e262f1494c1b2a55e
LinuxLinuxAffected
  • ≥ b194d21b9bcc15b50df1bc3ff7428e51c2918a6f, < 9ae85b0c1909b6c6bfd2636b04cdaf7f520bf2b5
Fixed in
  • 9ae85b0c1909b6c6bfd2636b04cdaf7f520bf2b5
LinuxLinuxAffected
  • ≥ b194d21b9bcc15b50df1bc3ff7428e51c2918a6f, < 0c44d61945c4a80775292d96460aa2f22e62f86c
Fixed in
  • 0c44d61945c4a80775292d96460aa2f22e62f86c
LinuxLinuxAffected
  • =6.11
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Use kvfree instead of kfree in amdgpu_gmc_get_nps_memranges() amdgpu_discovery_get_nps_info() internally allocates memory for ranges using kvcalloc(), which may use vmalloc() for large allocation. Using kfree() to release vmalloc memory will lead to a memory corruption. Use kvfree() to safely handle both kmalloc and vmalloc allocations. Compile tested only. Issue found using a prototype static analysis tool and code review.

References

Community reviews

Loading reviews…