Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2025-40288

Vulnerability in Linux kernel (CVE-2025-40288)

Summary

Vulnerability in Linux kernel (CVE-2025-40288). Risk of unauthorized operations or information disclosure. Exploitable via bdev.

Original description

The description as published by the source.

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…

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-40288 has been found in Linux kernel.
Attackers can target a specific entry point like bdev over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Linux kernel CVE-2025-40288" on the vendor's site.

CVE-2025-40288 (Linux kernel)
Attack surface: bdev / AMDGPU_INFO_VRAM_USAGE / fb_usage
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in Linux kernel. Attackers reach the vulnerable code path via bdev.

📍 Affected scope

Check the vendor advisory for the affected versions of Linux kernel. Attack surface: bdev / AMDGPU_INFO_VRAM_USAGE / fb_usage.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Linux kernel を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details