LiveActive security incident?Get immediate response
CVE Record

CVE-2024-49874: i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition

In the Linux kernel, the following vulnerability has been resolved: i3c: master: svc: Fix use after free vulnerability in svc_i3c_master Driver Due to Race Condition In the svc_i3c_master_probe function, &master->hj_work is bound with svc_i3c_master_hj_work, &master->ibi_work is bound with svc_i3c_master_ibi_work. And svc_i3c_master_ibi_work can start the hj_work, svc_i3c_master_irq_handler can start the ibi_work. If we remove the module which will call svc_i3c_master_remove to make cleanup, it will free master->base through i3c_master_unregister while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | svc_i3c_master_hj_work svc_i3c_master_remove | i3c_master_unregister(&master->base)| device_unregister(&master->dev) | device_release | //free master->base | | i3c_master_do_daa(&master->base) | //use master->base Fix it by ensuring that the work is canceled before proceeding with the cleanup in svc_i3c_master_remove.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A race condition in Linux’s SVC I3C master driver can leave background work using memory after it has been freed during driver removal. This may enable a local, low-privileged attacker to crash or potentially compromise an affected system. Exposure depends on the affected driver and lifecycle conditions being present.

Executive priority

Treat this as a high-priority targeted kernel update, especially for appliances or systems using the affected I3C controller driver. It is not supported as a broad internet emergency because exploitation is local, environment-dependent, and not reported as active in the supplied sources.

Technical view

The interrupt handler can schedule ibi_work, which can start hj_work. Driver removal may unregister and free master->base before this work completes, allowing i3c_master_do_daa to dereference freed memory. The stable fixes cancel pending work before cleanup.

Likely exposure

The bundle lists Linux 6.4, 6.6.55, 6.10.14, 6.11.3, and 6.12 as affected. Practical exposure is concentrated on systems using the svc_i3c_master driver. Exact downstream distribution package ranges are not provided and require vendor confirmation.

Exploitation context

The CVE is not listed in KEV, and the supplied sources do not report active exploitation or a public exploit. CVSS characterizes it as local, low-complexity exploitation requiring low privileges and no user interaction. Triggering also depends on the driver-removal race occurring.

Researcher notes

The source bundle assigns CVSS 3.1 score 7.8 with high confidentiality, integrity, and availability impacts but provides no CWE. Exact distribution exposure and exploit reliability remain unestablished. Review downstream backports because kernel package versions may not directly match upstream stable releases.

Mitigation direction

  • Apply the appropriate Linux stable fix or a downstream kernel package containing its backport.
  • Confirm the distribution’s patched package maps to an applicable cited stable commit.
  • Prioritize remediation on systems that actively use the svc_i3c_master driver.
  • Consult distribution or hardware-vendor guidance when branch-specific remediation status is unclear.

Validation and detection

  • Inventory running kernel releases and compare them with vendor advisories for CVE-2024-49874.
  • Determine whether the svc_i3c_master driver is present and active on each system.
  • Verify the installed kernel includes an applicable cited fix or documented downstream backport.
  • After updating, confirm the fixed kernel is running and monitor for driver-related crashes.
Prepared
Confidence
medium
Sources
7

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-49874 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
1ADP providers
6Source 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-49874Attack 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux87e0f28eda36c7843523aa8dd0c5dab3331e9718, 0f74f8b6675cc36d689abb4d9b3d75ab4049b7d7, 0f74f8b6675cc36d689abb4d9b3d75ab4049b7d7, 0f74f8b6675cc36d689abb4d9b3d75ab4049b7d7, 0f74f8b6675cc36d689abb4d9b3d75ab4049b7d7unaffected
LinuxLinux6.4, 0, 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.