LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46837: drm/panthor: Restrict high priorities on group_create

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A Linux graphics driver flaw allowed ordinary users to request high-priority Panthor GPU scheduling groups. That could let a local user or workload disrupt GPU availability, causing denial of service rather than data theft or remote compromise.

Executive priority

Treat this as a targeted availability risk, not a broad remote breach risk. Prioritize patching shared Linux systems with Panthor GPUs or exposed GPU access, and track vendor kernel updates for affected fleets.

Technical view

CVE-2024-46837 affects the Linux kernel DRM Panthor driver group_create ioctl. Permission checks were missing for priorities above PANTHOR_GROUP_PRIORITY_MEDIUM. The fix restricts higher priorities to DRM master or CAP_SYS_NICE users and leaves priority validity checks in panthor_group_create.

Likely exposure

Exposure is most likely on Linux systems using the Panthor DRM driver, especially devices or shared hosts with Arm Mali Panthor-supported GPUs and local untrusted users or workloads. Exact exposure depends on vendor kernel backports and enabled hardware.

Exploitation context

The source describes possible denial of service from unauthorized high-priority group creation. CISA KEV status is false in the bundle, and no provided source states active exploitation or public weaponization.

Researcher notes

The bundle lacks CVSS, CWE, and detailed affected distro mappings. Mesa is noted as hardcoding MEDIUM, suggesting normal Mesa use should remain compatible with the restriction. Avoid assuming impact beyond local denial of service.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Check distribution advisories for backported fixes to affected kernels.
  • Limit local access to DRM/Panthor devices where untrusted users share systems.
  • Review container or desktop policies that expose GPU device nodes.
  • Monitor vendor guidance; no separate workaround is named in the sources.

Validation and detection

  • Identify whether systems use the Linux Panthor DRM driver.
  • Map deployed kernel packages to vendor fixes or referenced stable commits.
  • Review whether untrusted users can access relevant DRM device nodes.
  • Confirm fixed kernels enforce CAP_SYS_NICE or DRM master for high priorities.
  • Prioritize shared GPU hosts over single-user endpoints.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-46837 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxde85488138247d034eb3241840424a54d660926b, de85488138247d034eb3241840424a54d660926bunaffected
LinuxLinux6.10, 0, 6.10.10, 6.11affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.