LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46829: rtmutex: Drop rt_mutex::wait_lock before scheduling

In the Linux kernel, the following vulnerability has been resolved: rtmutex: Drop rt_mutex::wait_lock before scheduling rt_mutex_handle_deadlock() is called with rt_mutex::wait_lock held. In the good case it returns with the lock held and in the deadlock case it emits a warning and goes into an endless scheduling loop with the lock held, which triggers the 'scheduling in atomic' warning. Unlock rt_mutex::wait_lock in the dead lock case before issuing the warning and dropping into the schedule for ever loop. [ tglx: Moved unlock before the WARN(), removed the pointless comment, massaged changelog, added Fixes tag ]

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in real-time mutex deadlock handling. In a deadlock path, the kernel could keep an internal lock held while scheduling, producing a kernel warning and potentially affecting system stability. The source bundle does not provide CVSS, CWE, or confirmed exploitation evidence.

Executive priority

Prioritize normal kernel security maintenance unless local context shows unstable real-time workloads or exposed critical infrastructure. There is no cited active exploitation or severity score, but kernel reliability bugs can still create operational risk.

Technical view

rt_mutex_handle_deadlock() is called while rt_mutex::wait_lock is held. In the deadlock case, it warned and entered an endless schedule loop without dropping the lock, triggering a scheduling-in-atomic warning. Stable kernel commits change this path to unlock before warning and scheduling.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or vendor kernels without the stable backport. The bundle lists affected Linux version entries including 3.16, 4.19.322, 5.4.284, 5.10.226, 5.15.167, 6.1.110, 6.6.51, 6.10.10, and 6.11.

Exploitation context

The bundle marks KEV as false and cites no active exploitation. It also does not describe attacker prerequisites, exploitability, or impact beyond the kernel deadlock warning behavior. Treat exploitation status as unconfirmed, not active.

Researcher notes

The public record gives a narrow kernel locking defect and fix rationale, but lacks CVSS, CWE, exploit prerequisites, and concrete impact classification. Validation should focus on kernel source/package backport evidence, not only reported version strings.

Mitigation direction

  • Inventory Linux kernel versions across servers, appliances, and container hosts.
  • Apply kernel updates that include the referenced upstream stable commits.
  • For Debian systems, review the referenced Debian LTS advisories and install security updates.
  • Check distribution vendor guidance for backported fixes before relying on upstream version numbers.

Validation and detection

  • Compare running kernel builds against vendor advisories and package changelogs.
  • Confirm the relevant stable commit is present in custom or self-built kernels.
  • Verify patched systems rebooted into the updated kernel.
  • Monitor kernel logs for related rtmutex or scheduling-in-atomic warnings.
Prepared
Confidence
medium
Sources
12

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-46829 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
2ADP providers
11Source 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
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3d5c9340d1949733eb37616abd15db36aef9a57c, 3d5c9340d1949733eb37616abd15db36aef9a57c, 3d5c9340d1949733eb37616abd15db36aef9a57c, 3d5c9340d1949733eb37616abd15db36aef9a57c, 3d5c9340d1949733eb37616abd15db36aef9a57c, 3d5c9340d1949733eb37616abd15db36aef9a57c, 3d5c9340d1949733eb37616abd15db36aef9a57c, 3d5c9340d1949733eb37616abd15db36aef9a57c, 95f9aded9436aa3ce714aeff3f45fcc1431df7d2, ea018da95368adfb700689bd9842714f7c3db665, 1201613a70dd34bd347ba2970919b3f1d5fbfb4a, a2e64fcdc83c645813f7b93e4df291841ba7c625, fb52f40e085ef4074f1335672cd62c1f832af13b, 2b1f3807ed9cafb59c956ce76a05d25e67103f2e, 3.2.61, 3.4.99, 3.10.49, 3.12.25, 3.14.10, 3.15.3unaffected
LinuxLinux3.16, 0, 4.19.322, 5.4.284, 5.10.226, 5.15.167, 6.1.110, 6.6.51, 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.