Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/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.20% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1401da1486dc1cdbef6025fd74a3977df3a3e5d0, 3.11, 3.13; Azure Linux 3.0 ARM 6.6.51.1-5; Azure Linux 3.0 x64 6.6.51.1-5.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 1401da1486dc1cdbef6025fd74a3977df3a3e5d0, 3.11, 3.13; Azure Linux 3.0 ARM 6.6.51.1-5; Azure Linux 3.0 x64 6.6.51.1-5 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: 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 ]

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Sep 27, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 10th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 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-46829

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 instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack 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 (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

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

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

Affected versions

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

  • linux linux kernel3.2.61 and later · before 3.3
  • linux linux kernel3.4.99 and later · before 3.5
  • linux linux kernel3.10.49 and later · before 3.11
  • linux linux kernel3.12.25 and later · before 3.13
  • linux linux kernel3.14.10 and later · before 3.15
  • linux linux kernel3.15.3 and later · before 3.16
  • linux linux kernel3.16 and later · before 4.19.322
  • linux linux kernel4.20 and later · before 5.4.284
  • linux linux kernel5.5 and later · before 5.10.226
  • linux linux kernel5.11 and later · before 5.15.167
  • linux linux kernel5.16 and later · before 6.1.110
  • linux linux kernel6.2 and later · before 6.6.51
  • linux linux kernel6.7 and later · before 6.10.10
  • linux linux kernel6.11

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

    • 95f9aded9436aa3ce714aeff3f45fcc1431df7d2, ea018da95368adfb700689bd9842714f7c3db665, 1201613a70dd34bd347ba2970919b3f1d5fbfb4a, a2e64fcdc83c645813f7b93e4df291841ba7c625, fb52f40e085ef4074f1335672cd62c1f832af13b, 2b1f3807ed9cafb59c956ce76a05d25e67103f2e, 3.16affected
    • 3d5c9340d1949733eb37616abd15db36aef9a57c and later · before 432efdbe7da5ecfcbc0c2180cfdbab1441752a38affected · git
    • 3d5c9340d1949733eb37616abd15db36aef9a57c and later · before 6a976e9a47e8e5b326de671811561cab12e6fb1faffected · git
    • 3d5c9340d1949733eb37616abd15db36aef9a57c and later · before 1401da1486dc1cdbef6025fd74a3977df3a3e5d0affected · git
    • 3d5c9340d1949733eb37616abd15db36aef9a57c and later · before 93f44655472d9cd418293d328f9d141ca234ad83affected · git
    • 3d5c9340d1949733eb37616abd15db36aef9a57c and later · before a92d81c9efec9280681c27a2c0a963fd0f1338e0affected · git
    • 3d5c9340d1949733eb37616abd15db36aef9a57c and later · before 85f03ca98e07cd0786738b56ae73740bce0ac27faffected · git
    • 3d5c9340d1949733eb37616abd15db36aef9a57c and later · before f13b5afc5c4889569d84c3011ce449f61fccfb28affected · git
    • 3d5c9340d1949733eb37616abd15db36aef9a57c and later · before d33d26036a0274b472299d7dcdaa5fb34329f91baffected · git
    • 3.2.61 and later · before 3.3affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.112-16.1.112-1
Debian:13linuxbefore 6.10.11-16.10.11-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-46827Sep 27, 2024 · wifi: ath12k: fix firmware crash due to invalid peer nss
    22Monitor
  • ← EarlierCVE-2024-46828Sep 27, 2024 · sched: sch_cake: fix bulk flow accounting logic for host fairness
    31Monitor
  • Later →CVE-2024-46830Sep 27, 2024 · KVM: x86: Acquire kvm->srcu when handling KVM_SET_VCPU_EVENTS
    31Monitor

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 Linux1401da1486dc1cdbef6025fd74a3977df3a3e5d0Vendor (CNA)
Linux Linux3.11Vendor (CNA)
Linux Linux3.13Vendor (CNA)
Linux Linux3.15Vendor (CNA)
Linux Linux3.16Vendor (CNA)
Linux Linux3.3Vendor (CNA)
Linux Linux3.5Vendor (CNA)
Linux Linux432efdbe7da5ecfcbc0c2180cfdbab1441752a38Vendor (CNA)
Linux Linux6a976e9a47e8e5b326de671811561cab12e6fb1fVendor (CNA)
Linux Linux85f03ca98e07cd0786738b56ae73740bce0ac27fVendor (CNA)
Linux Linux93f44655472d9cd418293d328f9d141ca234ad83Vendor (CNA)
Linux Linuxa92d81c9efec9280681c27a2c0a963fd0f1338e0Vendor (CNA)
Linux Linuxd33d26036a0274b472299d7dcdaa5fb34329f91bVendor (CNA)
Linux Linuxf13b5afc5c4889569d84c3011ce449f61fccfb28Vendor (CNA)
Azure Linux 3.0 ARM6.6.51.1-5 · kernelMicrosoft (MSRC)
Azure Linux 3.0 x646.6.51.1-5 · kernelMicrosoft (MSRC)
CBL Mariner 2.0 ARM5.15.167.1-1 · kernelMicrosoft (MSRC)
CBL Mariner 2.0 x645.15.167.1-1 · kernelMicrosoft (MSRC)
debian:linux6.1.112-1 · Debian:12Package 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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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.
  • No special conditions are required; it is repeatable.

If successful

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

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

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

nvd-primary

Attack context

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

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records