CVE-2024-46837: Vulnerability in Linux Linux
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Restrict high priorities on group_create We were allowing any users to create a high priority group without any permission checks. As a result, this was allowing possible denial of service. We now only allow the DRM master or users with the CAP_SYS_NICE capability to set higher priorities than PANTHOR_GROUP_PRIORITY_MEDIUM. As the sole user of that uAPI lives in Mesa and hardcode a value of MEDIUM [1], this should be safe to do. Additionally, as those checks are performed at the ioctl level, panthor_group_create now only check for priority level validity. [1]https://gitlab.freedesktop.org/mesa/mesa/-/blob/f390835074bdf162a63deb0311d1a6de527f9f89/src/gallium/drivers/panfrost/pan_csf.c#L1038
AI Analysis
Technical Summary
CVE-2024-46837 is a vulnerability identified in the Linux kernel's Direct Rendering Manager (DRM) subsystem, specifically within the Panthor driver component used by the Panfrost GPU driver stack. The issue arises from insufficient permission checks when creating groups with high scheduling priorities. Originally, any user was able to create a high priority group without restrictions, which could lead to denial of service (DoS) conditions by allowing unprivileged users to monopolize CPU scheduling resources. The vulnerability stems from the panthor_group_create ioctl interface, which did not enforce adequate permission validation for priority levels above PANTHOR_GROUP_PRIORITY_MEDIUM. The fix restricts the ability to assign priorities higher than medium to only the DRM master or users possessing the CAP_SYS_NICE capability, which is a privileged capability allowing modification of process scheduling priorities. Since the only known user of this interface is Mesa's Panfrost driver, which hardcodes the priority to medium, this change is expected to be safe and not break legitimate functionality. The checks are now performed at the ioctl level, ensuring that unauthorized users cannot escalate priority levels and cause resource starvation. No known exploits are currently reported in the wild, and the vulnerability was published on September 27, 2024. This vulnerability primarily affects Linux kernel versions containing the specified commit hashes prior to the patch. The root cause is a lack of permission enforcement on scheduling priority assignment in a GPU driver context, which could be exploited to degrade system availability by causing CPU resource exhaustion or starvation of critical processes.
Potential Impact
For European organizations, this vulnerability poses a risk primarily in environments running Linux systems with the affected kernel versions and utilizing the Panfrost GPU driver, which is common in ARM-based devices and some embedded systems. The potential impact is a denial of service condition where unprivileged users could degrade system performance or cause critical services to become unresponsive by creating high priority groups that monopolize CPU scheduling. This could affect servers, workstations, or embedded devices used in industrial control, telecommunications, or cloud infrastructure. Organizations relying on Linux-based infrastructure with GPU acceleration or graphical workloads could see availability disruptions. Although the vulnerability does not directly compromise confidentiality or integrity, the availability impact could interrupt business operations, especially in sectors requiring high uptime such as finance, healthcare, and critical infrastructure. The absence of known exploits reduces immediate risk, but the ease of exploitation (no authentication required beyond local user access) means insider threats or compromised accounts could leverage this vulnerability. European organizations with multi-user Linux environments or shared hosting platforms are particularly at risk if they do not restrict user capabilities properly.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should: 1) Apply the latest Linux kernel patches that include the fix restricting high priority group creation to privileged users only. 2) Audit and restrict CAP_SYS_NICE capability assignments to trusted users only, minimizing the number of users who can manipulate scheduling priorities. 3) Implement strict user privilege separation and avoid granting unnecessary permissions to unprivileged users, especially on systems with GPU acceleration. 4) Monitor system logs and ioctl calls related to DRM and Panfrost driver activity for unusual priority escalation attempts. 5) For environments where patching is delayed, consider disabling or restricting access to the Panfrost driver if not required. 6) Employ resource control mechanisms such as cgroups or systemd slices to limit CPU resource usage per user or group, mitigating potential DoS impact. 7) Educate system administrators about this vulnerability and ensure proper kernel version management and vulnerability scanning are part of routine security operations.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Norway, Denmark
CVE-2024-46837: Vulnerability in Linux Linux
Description
In the Linux kernel, the following vulnerability has been resolved: drm/panthor: Restrict high priorities on group_create We were allowing any users to create a high priority group without any permission checks. As a result, this was allowing possible denial of service. We now only allow the DRM master or users with the CAP_SYS_NICE capability to set higher priorities than PANTHOR_GROUP_PRIORITY_MEDIUM. As the sole user of that uAPI lives in Mesa and hardcode a value of MEDIUM [1], this should be safe to do. Additionally, as those checks are performed at the ioctl level, panthor_group_create now only check for priority level validity. [1]https://gitlab.freedesktop.org/mesa/mesa/-/blob/f390835074bdf162a63deb0311d1a6de527f9f89/src/gallium/drivers/panfrost/pan_csf.c#L1038
AI-Powered Analysis
Technical Analysis
CVE-2024-46837 is a vulnerability identified in the Linux kernel's Direct Rendering Manager (DRM) subsystem, specifically within the Panthor driver component used by the Panfrost GPU driver stack. The issue arises from insufficient permission checks when creating groups with high scheduling priorities. Originally, any user was able to create a high priority group without restrictions, which could lead to denial of service (DoS) conditions by allowing unprivileged users to monopolize CPU scheduling resources. The vulnerability stems from the panthor_group_create ioctl interface, which did not enforce adequate permission validation for priority levels above PANTHOR_GROUP_PRIORITY_MEDIUM. The fix restricts the ability to assign priorities higher than medium to only the DRM master or users possessing the CAP_SYS_NICE capability, which is a privileged capability allowing modification of process scheduling priorities. Since the only known user of this interface is Mesa's Panfrost driver, which hardcodes the priority to medium, this change is expected to be safe and not break legitimate functionality. The checks are now performed at the ioctl level, ensuring that unauthorized users cannot escalate priority levels and cause resource starvation. No known exploits are currently reported in the wild, and the vulnerability was published on September 27, 2024. This vulnerability primarily affects Linux kernel versions containing the specified commit hashes prior to the patch. The root cause is a lack of permission enforcement on scheduling priority assignment in a GPU driver context, which could be exploited to degrade system availability by causing CPU resource exhaustion or starvation of critical processes.
Potential Impact
For European organizations, this vulnerability poses a risk primarily in environments running Linux systems with the affected kernel versions and utilizing the Panfrost GPU driver, which is common in ARM-based devices and some embedded systems. The potential impact is a denial of service condition where unprivileged users could degrade system performance or cause critical services to become unresponsive by creating high priority groups that monopolize CPU scheduling. This could affect servers, workstations, or embedded devices used in industrial control, telecommunications, or cloud infrastructure. Organizations relying on Linux-based infrastructure with GPU acceleration or graphical workloads could see availability disruptions. Although the vulnerability does not directly compromise confidentiality or integrity, the availability impact could interrupt business operations, especially in sectors requiring high uptime such as finance, healthcare, and critical infrastructure. The absence of known exploits reduces immediate risk, but the ease of exploitation (no authentication required beyond local user access) means insider threats or compromised accounts could leverage this vulnerability. European organizations with multi-user Linux environments or shared hosting platforms are particularly at risk if they do not restrict user capabilities properly.
Mitigation Recommendations
To mitigate this vulnerability, European organizations should: 1) Apply the latest Linux kernel patches that include the fix restricting high priority group creation to privileged users only. 2) Audit and restrict CAP_SYS_NICE capability assignments to trusted users only, minimizing the number of users who can manipulate scheduling priorities. 3) Implement strict user privilege separation and avoid granting unnecessary permissions to unprivileged users, especially on systems with GPU acceleration. 4) Monitor system logs and ioctl calls related to DRM and Panfrost driver activity for unusual priority escalation attempts. 5) For environments where patching is delayed, consider disabling or restricting access to the Panfrost driver if not required. 6) Employ resource control mechanisms such as cgroups or systemd slices to limit CPU resource usage per user or group, mitigating potential DoS impact. 7) Educate system administrators about this vulnerability and ensure proper kernel version management and vulnerability scanning are part of routine security operations.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Linux
- Date Reserved
- 2024-09-11T15:12:18.288Z
- Cisa Enriched
- true
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 682d9825c4522896dcbe02b0
Added to database: 5/21/2025, 9:08:53 AM
Last enriched: 6/28/2025, 6:39:53 PM
Last updated: 8/16/2025, 2:06:27 PM
Views: 17
Related Threats
CVE-2025-53948: CWE-415 Double Free in Santesoft Sante PACS Server
HighCVE-2025-52584: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-46269: CWE-122 Heap-based Buffer Overflow in Ashlar-Vellum Cobalt
HighCVE-2025-54862: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumCVE-2025-54759: CWE-79 Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') in Santesoft Sante PACS Server
MediumActions
Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.