LiveActive security incident?Get immediate response
CVE Record

CVE-2024-49981: media: venus: fix use after free bug in venus_remove due to race condition

In the Linux kernel, the following vulnerability has been resolved: media: venus: fix use after free bug in venus_remove due to race condition in venus_probe, core->work is bound with venus_sys_error_handler, which is used to handle error. The code use core->sys_err_done to make sync work. The core->work is started in venus_event_notify. If we call venus_remove, there might be an unfished work. The possible sequence is as follows: CPU0 CPU1 |venus_sys_error_handler venus_remove | hfi_destroy | venus_hfi_destroy | kfree(hdev); | |hfi_reinit |venus_hfi_queues_reinit |//use hdev Fix it by canceling the work in venus_remove.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A race condition in the Linux Venus media driver can let background error-handling work access memory after device removal has freed it. A successful local attack could potentially compromise confidentiality, integrity, and availability. The supplied CVSS score is 7.8, but practical exposure depends on the vulnerable driver and kernel code being present and reachable.

Executive priority

Prioritize patch verification for multi-user or otherwise untrusted Linux systems using the Venus media driver. Treat exposed systems as high priority because potential impact spans data confidentiality, system integrity, and availability. Systems without the affected driver or reachable local users are lower urgency after validation.

Technical view

During venus_remove, venus_hfi_destroy can free hdev while venus_sys_error_handler continues and reaches hfi_reinit or venus_hfi_queues_reinit, producing a use-after-free. The upstream fix cancels pending work during removal. The CVSS vector indicates local access, low complexity, low privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Likely exposure is limited to Linux systems containing a vulnerable Venus media driver where a local low-privileged user can reach the affected device lifecycle or error-handling path. The supplied version data is ambiguous, so kernel or distribution patch status should be verified directly rather than inferred from version numbers alone.

Exploitation context

The bundle does not identify public exploitation, exploit code, or observed attacks, and the CVE is not listed as KEV. Exploitation requires local access with low privileges according to the supplied CVSS vector. The race condition may make exploitation timing-dependent, but the source does not establish practical reliability.

Researcher notes

The central condition is teardown racing with queued venus_sys_error_handler work after hdev is freed. Review whether cancellation is synchronous and occurs before HFI destruction in the applicable backport. The bundle provides multiple stable commits but does not map each commit clearly to affected and fixed release boundaries.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable stable fix.
  • Check distribution security advisories before relying on kernel version numbers alone.
  • Restrict untrusted local access while affected systems await updates.
  • Disable the affected driver only if operationally acceptable and vendor-supported.

Validation and detection

  • Inventory kernel builds on systems using the Venus media driver.
  • Confirm the applicable stable commit or distribution backport is present.
  • Verify scanners recognize vendor backports and do not rely solely on version strings.
  • Regression-test driver removal and error handling after updating.
Prepared
Confidence
medium
Sources
5

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-49981 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
2ADP providers
12Source links

SSVC decision data

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

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-2024-49981Attack 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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxaf2c3834c8ca7cc65d15592ac671933df8848115, af2c3834c8ca7cc65d15592ac671933df8848115, af2c3834c8ca7cc65d15592ac671933df8848115, af2c3834c8ca7cc65d15592ac671933df8848115, af2c3834c8ca7cc65d15592ac671933df8848115, af2c3834c8ca7cc65d15592ac671933df8848115, af2c3834c8ca7cc65d15592ac671933df8848115, af2c3834c8ca7cc65d15592ac671933df8848115, af2c3834c8ca7cc65d15592ac671933df8848115unaffected
LinuxLinux4.13, 0, 4.19.323, 5.4.285, 5.10.227, 5.15.168, 6.1.113, 6.6.55, 6.10.14, 6.11.3, 6.12affected
Weakness

CWE details

No CWE listed

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