CVE-2025-37965: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix invalid context error in dml helper [Why] "BUG: sleeping function called from invalid context" error. after: "drm/amd/display: Protect FPU in dml2_validate()/dml21_validate()" The populate_dml_plane_cfg_from_plane_state() uses the GFP_KERNEL flag for memory allocation, which shouldn't be used in atomic contexts. The allocation is needed only for using another helper function get_scaler_data_for_plane(). [How] Modify helpers to pass a pointer to scaler_data within existing context, eliminating the need for dynamic memory allocation/deallocation and copying. (cherry picked from commit bd3e84bc98f81b44f2c43936bdadc3241d654259)
AI Analysis
Technical Summary
CVE-2025-37965 is a vulnerability identified in the Linux kernel specifically within the Direct Rendering Manager (DRM) subsystem for AMD display drivers. The issue arises from improper memory allocation practices in the function populate_dml_plane_cfg_from_plane_state(), which uses the GFP_KERNEL flag for memory allocation. This flag is inappropriate in atomic contexts where sleeping is disallowed, leading to a "BUG: sleeping function called from invalid context" error. The root cause is that the function attempts to allocate memory dynamically in a context that does not permit sleeping, which can cause kernel instability or crashes. The vulnerability was addressed by modifying helper functions to pass pointers to scaler_data within the existing context, thereby eliminating the need for dynamic memory allocation and deallocation during atomic operations. This fix prevents the kernel from invoking sleeping functions in invalid contexts, enhancing stability and security. The vulnerability affects specific Linux kernel versions identified by their commit hashes, and no known exploits are currently reported in the wild. The flaw is technical and relates to kernel memory management and context handling in the AMD DRM display driver, which is critical for graphical output on systems using AMD GPUs.
Potential Impact
For European organizations, the impact of CVE-2025-37965 primarily concerns systems running vulnerable Linux kernel versions with AMD GPU hardware utilizing the DRM subsystem. Potential impacts include kernel panics or system crashes due to improper memory allocation in atomic contexts, which can lead to denial of service (DoS) conditions. This could disrupt critical services, especially in environments relying on Linux servers or workstations with AMD graphics hardware for graphical processing or display tasks. While the vulnerability does not appear to allow privilege escalation or remote code execution, the resulting instability could affect availability and operational continuity. Organizations in sectors such as finance, manufacturing, research, and public administration that depend on Linux-based infrastructure may experience service interruptions or degraded performance. Additionally, the lack of known exploits reduces immediate risk, but unpatched systems remain vulnerable to potential future exploitation or accidental crashes triggered by normal operations involving the affected driver code.
Mitigation Recommendations
European organizations should prioritize updating their Linux kernel to versions that include the patch for CVE-2025-37965. Specifically, they should track kernel updates from their Linux distribution vendors that incorporate the fix described (commit bd3e84bc98f81b44f2c43936bdadc3241d654259). System administrators should audit their environments to identify systems running affected kernel versions and AMD GPU hardware using the DRM subsystem. Where immediate patching is not feasible, organizations can consider temporarily disabling or limiting the use of AMD DRM drivers if possible, or isolating affected systems to reduce impact. Monitoring kernel logs for the specific 'BUG: sleeping function called from invalid context' error can help detect attempts to trigger the vulnerability or system instability. Additionally, organizations should maintain robust backup and recovery procedures to mitigate potential service disruptions. Coordination with Linux distribution maintainers and AMD for timely updates and advisories is recommended to ensure ongoing protection.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Poland, Italy, Spain
CVE-2025-37965: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix invalid context error in dml helper [Why] "BUG: sleeping function called from invalid context" error. after: "drm/amd/display: Protect FPU in dml2_validate()/dml21_validate()" The populate_dml_plane_cfg_from_plane_state() uses the GFP_KERNEL flag for memory allocation, which shouldn't be used in atomic contexts. The allocation is needed only for using another helper function get_scaler_data_for_plane(). [How] Modify helpers to pass a pointer to scaler_data within existing context, eliminating the need for dynamic memory allocation/deallocation and copying. (cherry picked from commit bd3e84bc98f81b44f2c43936bdadc3241d654259)
AI-Powered Analysis
Technical Analysis
CVE-2025-37965 is a vulnerability identified in the Linux kernel specifically within the Direct Rendering Manager (DRM) subsystem for AMD display drivers. The issue arises from improper memory allocation practices in the function populate_dml_plane_cfg_from_plane_state(), which uses the GFP_KERNEL flag for memory allocation. This flag is inappropriate in atomic contexts where sleeping is disallowed, leading to a "BUG: sleeping function called from invalid context" error. The root cause is that the function attempts to allocate memory dynamically in a context that does not permit sleeping, which can cause kernel instability or crashes. The vulnerability was addressed by modifying helper functions to pass pointers to scaler_data within the existing context, thereby eliminating the need for dynamic memory allocation and deallocation during atomic operations. This fix prevents the kernel from invoking sleeping functions in invalid contexts, enhancing stability and security. The vulnerability affects specific Linux kernel versions identified by their commit hashes, and no known exploits are currently reported in the wild. The flaw is technical and relates to kernel memory management and context handling in the AMD DRM display driver, which is critical for graphical output on systems using AMD GPUs.
Potential Impact
For European organizations, the impact of CVE-2025-37965 primarily concerns systems running vulnerable Linux kernel versions with AMD GPU hardware utilizing the DRM subsystem. Potential impacts include kernel panics or system crashes due to improper memory allocation in atomic contexts, which can lead to denial of service (DoS) conditions. This could disrupt critical services, especially in environments relying on Linux servers or workstations with AMD graphics hardware for graphical processing or display tasks. While the vulnerability does not appear to allow privilege escalation or remote code execution, the resulting instability could affect availability and operational continuity. Organizations in sectors such as finance, manufacturing, research, and public administration that depend on Linux-based infrastructure may experience service interruptions or degraded performance. Additionally, the lack of known exploits reduces immediate risk, but unpatched systems remain vulnerable to potential future exploitation or accidental crashes triggered by normal operations involving the affected driver code.
Mitigation Recommendations
European organizations should prioritize updating their Linux kernel to versions that include the patch for CVE-2025-37965. Specifically, they should track kernel updates from their Linux distribution vendors that incorporate the fix described (commit bd3e84bc98f81b44f2c43936bdadc3241d654259). System administrators should audit their environments to identify systems running affected kernel versions and AMD GPU hardware using the DRM subsystem. Where immediate patching is not feasible, organizations can consider temporarily disabling or limiting the use of AMD DRM drivers if possible, or isolating affected systems to reduce impact. Monitoring kernel logs for the specific 'BUG: sleeping function called from invalid context' error can help detect attempts to trigger the vulnerability or system instability. Additionally, organizations should maintain robust backup and recovery procedures to mitigate potential service disruptions. Coordination with Linux distribution maintainers and AMD for timely updates and advisories is recommended to ensure ongoing protection.
Affected Countries
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2025-04-16T04:51:23.974Z
- Cisa Enriched
- false
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682cd0f71484d88663aeae20
Added to database: 5/20/2025, 6:59:03 PM
Last enriched: 7/3/2025, 7:10:03 PM
Last updated: 1/7/2026, 6:07:23 AM
Views: 56
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-14835: CWE-80 Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) in opajaap WP Photo Album Plus
HighCVE-2026-0650: CWE-306 Missing Authentication for Critical Function in OpenFlagr Flagr
CriticalCVE-2025-15474: CWE-770 Allocation of Resources Without Limits or Throttling in AuntyFey AuntyFey Smart Combination Lock
MediumCVE-2025-14468: CWE-352 Cross-Site Request Forgery (CSRF) in mohammed_kaludi AMP for WP – Accelerated Mobile Pages
MediumCVE-2025-9611: CWE-749 Exposed Dangerous Method or Function in Microsoft Playwright
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.