CVE-2025-40288

CVE-2025-40288 is a unknown-severity security vulnerability. No fixed version is listed yet.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix NULL pointer...

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: Fix NULL pointer dereference in VRAM logic for APU devices

Previously, APU platforms (and other scenarios with uninitialized VRAM managers)
triggered a NULL pointer dereference in ttm_resource_manager_usage(). The root
cause is not that the struct ttm_resource_manager *man pointer itself is NULL,
but that man->bdev (the backing device pointer within the manager) remains
uninitialized (NULL) on APUs, since APUs lack dedicated VRAM and do not fully
set up VRAM manager structures. When ttm_resource_manager_usage() attempts to
acquire man->bdev->lru_lock, it dereferences the NULL man->bdev, leading to
a kernel OOPS.

  1. amdgpu_cs.c: Extend the existing bandwidth control check in
    amdgpu_cs_get_threshold_for_moves() to include a check for
    ttm_resource_manager_used(). If the manager is not used (uninitialized
    bdev), return 0 for migration thresholds immediately, skipping VRAM-specific
    logic that would trigger the NULL dereference.

  2. amdgpu_kms.c: Update the AMDGPU_INFO_VRAM_USAGE ioctl and memory info
    reporting to use a conditional: if the manager is used, return the real VRAM
    usage; otherwise, return 0. This avoids accessing man->bdev when it is
    NULL.

  3. amdgpu_virt.c: Modify the vf2pf (virtual function to physical function)
    data write path. Use ttm_resource_manager_used() to check validity: if the
    manager is usable, calculate fb_usage from VRAM usage; otherwise, set
    fb_usage to 0 (APUs have no discrete framebuffer to report).

This approach is more robust than APU-specific checks because it:

  • Works for all scenarios where the VRAM manager is uninitialized (not just APUs),
  • Aligns with TTM's design by using its native helper function,
  • Preserves correct behavior for discrete GPUs (which have fully initialized
    man->bdev and pass the ttm_resource_manager_used() check).

v4: use ttm_resource_manager_used(&adev->mman.vram_mgr.manager) instead of checking the adev->gmc.is_app_apu flag (Christian)

Impact

Affected versions

Not available

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Not available

Frequently Asked Questions

  1. What is CVE-2025-40288? CVE-2025-40288 is a unknown-severity security vulnerability. No fixed version is listed yet.
  2. Is there a fix for CVE-2025-40288? No fixed version is listed for CVE-2025-40288 yet. Monitor the advisory for updates and apply mitigations in the interim.
  3. Is CVE-2025-40288 exploitable, and should I be worried? Whether CVE-2025-40288 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  4. What actually determines whether CVE-2025-40288 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Stop the waste.
Protect your environment with Kodem.