LiveActive security incident?Get immediate response
CVE Record

CVE-2025-39785: drm/hisilicon/hibmc: fix irq_request()'s irq name variable is local

In the Linux kernel, the following vulnerability has been resolved: drm/hisilicon/hibmc: fix irq_request()'s irq name variable is local The local variable is passed in request_irq (), and there will be use after free problem, which will make request_irq failed. Using the global irq name instead of it to fix.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux graphics driver passes a short-lived local name to the interrupt-registration system, creating a use-after-free condition that can cause interrupt setup to fail. The supplied CVSS assessment rates potential confidentiality, integrity, and availability impact as high, but the source bundle does not demonstrate those outcomes in practice.

Executive priority

Treat this as a high-priority kernel maintenance issue on systems using hibmc, especially where untrusted users have local access. Scope the driver footprint first, then apply vendor-supported corrected kernels. Broad emergency action across all Linux hosts is not supported by the supplied evidence.

Technical view

The hibmc DRM driver supplied request_irq() with storage from a local variable whose lifetime ended too soon. Later use could access freed memory and make request_irq() fail. The referenced stable-kernel changes replace that local value with a globally persistent IRQ name.

Likely exposure

Exposure is limited to Linux systems using the affected hibmc driver and listed kernel versions. The bundle identifies versions around 6.16 through 6.17, but its version-range formatting is ambiguous. Confirm exposure using distribution advisories and whether the referenced fixes are present in the deployed kernel.

Exploitation context

The CVSS vector describes a local, low-complexity issue requiring low privileges and no user interaction. The CVE is not listed in KEV, and the supplied sources provide no evidence of active exploitation, public weaponization, or a reliable security-impact pathway beyond the reported use-after-free and interrupt-registration failure.

Researcher notes

The disclosed defect is a lifetime error involving the IRQ name passed to request_irq(). The stated observable result is registration failure. Although CVSS assigns high confidentiality, integrity, and availability impacts, the sources do not explain an exploitation primitive, affected hardware requirements, or how the memory-lifetime flaw produces those impacts.

Mitigation direction

  • Upgrade to a vendor-supported kernel containing either referenced stable fix.
  • Check distribution or appliance guidance for the exact corrected package version.
  • Prioritize systems that use the hibmc driver and expose local access.
  • If immediate upgrading is impossible, request vendor-supported mitigation guidance.

Validation and detection

  • Inventory deployed kernel versions and identify systems using the hibmc driver.
  • Confirm whether either referenced fix is included in each kernel build.
  • After updating, verify hibmc interrupt initialization succeeds without related errors.
  • Review vendor advisories because the supplied affected-version range is ambiguous.
Prepared
Confidence
medium
Sources
4

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-2025-39785 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-39785Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb11bc1ae46587f3563c47078e605184f18e7fa57, b11bc1ae46587f3563c47078e605184f18e7fa57unaffected
LinuxLinux6.16, 0, 6.16.4, 6.17affected
Weakness

CWE details

No CWE listed

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