Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-50061: i3c: master: cdns: Fix use after free vulnerability in cdns_i3c_master Driver Due to Race Condition

HighCVSS 7.0 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 2a21bad9964c91b34d65ba269914233720c0b1ce, 609366e7a06d035990df78f1562291c3bf0d4a12, 687016d6a1efbfacdd2af913e2108de6b75a28d5; azl3 kernel 6.6.56.1-5 on Azure Linux 3.0 6.6.57.1-1; azl3 kernel 6.6.57.1-1 on Azure Linux 3.0 6.6.57.1-1.

Low priority for now. Upgrade to Linux Linux 2a21bad9964c91b34d65ba269914233720c0b1ce, 609366e7a06d035990df78f1562291c3bf0d4a12, 687016d6a1efbfacdd2af913e2108de6b75a28d5; azl3 kernel 6.6.56.1-5 on Azure Linux 3.0 6.6.57.1-1; azl3 kernel 6.6.57.1-1 on Azure Linux 3.0 6.6.57.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: i3c: master: cdns: Fix use after free vulnerability in cdns_i3c_master Driver Due to Race Condition In the cdns_i3c_master_probe function, &master->hj_work is bound with cdns_i3c_master_hj. And cdns_i3c_master_interrupt can call cnds_i3c_master_demux_ibis function to start the work. If we remove the module which will call cdns_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 | cdns_i3c_master_hj cdns_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 cdns_i3c_master_remove.

Published
Oct 21, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 11th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-50061

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.0affected
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 2a21bad9964c91b34d65ba269914233720c0b1ceaffected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before ea0256e393e0072e8c80fd941547807f0c28108baffected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 687016d6a1efbfacdd2af913e2108de6b75a28d5affected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 609366e7a06d035990df78f1562291c3bf0d4a12affected · git
    • before 5.0not affected · semver
    • 6.1.129 and later · up to and including 6.1.*not affected · semver
    • 6.6.57 and later · up to and including 6.6.*not affected · semver
    • 6.11.4 and later · up to and including 6.11.*not affected · semver
    • 6.12 and laternot affected · original_commit_for_fix

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 6.6.57
  • linux linux kernel6.7 and later · before 6.11.4

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11linux-6.1before 6.1.129-1~deb11u16.1.129-1~deb11u1
Debian:12linuxbefore 6.1.129-16.1.129-1
Debian:13linuxbefore 6.11.4-16.11.4-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-50059Oct 21, 2024 · ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition
    28Monitor
  • ← EarlierCVE-2024-50060Oct 21, 2024 · io_uring: check if we need to reschedule during overflow flush
    22Monitor
  • Later →CVE-2024-50062Oct 21, 2024 · RDMA/rtrs-srv: Avoid null pointer deref during path establishment
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2a21bad9964c91b34d65ba269914233720c0b1ceVendor (CNA)
Linux Linux609366e7a06d035990df78f1562291c3bf0d4a12Vendor (CNA)
Linux Linux687016d6a1efbfacdd2af913e2108de6b75a28d5Vendor (CNA)
Linux Linuxea0256e393e0072e8c80fd941547807f0c28108bVendor (CNA)
azl3 kernel 6.6.56.1-5 on Azure Linux 3.06.6.57.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.57.1-1 on Azure Linux 3.06.6.57.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.129-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.129-1~deb11u1 · Debian:11Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records