Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-50006: ext4: fix i_data_sem unlock order in ext4_ind_migrate()

Noroxi assessment

Priority: Monitor (action score 18/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.19% (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 3c46d6060d3e38de22196c1fe7706c5a3c696285, 4192adefc9c570698821c5eb9873320eac2fcbf1, 53b1999cfd2c7addf2e581a32865fe8835467b44; Azure Linux 3.0 ARM 6.6.57.1-2; Azure Linux 3.0 x64 6.6.57.1-2.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 3c46d6060d3e38de22196c1fe7706c5a3c696285, 4192adefc9c570698821c5eb9873320eac2fcbf1, 53b1999cfd2c7addf2e581a32865fe8835467b44; Azure Linux 3.0 ARM 6.6.57.1-2; Azure Linux 3.0 x64 6.6.57.1-2 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: ext4: fix i_data_sem unlock order in ext4_ind_migrate() Fuzzing reports a possible deadlock in jbd2_log_wait_commit. This issue is triggered when an EXT4_IOC_MIGRATE ioctl is set to require synchronous updates because the file descriptor is opened with O_SYNC. This can lead to the jbd2_journal_stop() function calling jbd2_might_wait_for_commit(), potentially causing a deadlock if the EXT4_IOC_MIGRATE call races with a write(2) system call. This problem only arises when CONFIG_PROVE_LOCKING is enabled. In this case, the jbd2_might_wait_for_commit macro locks jbd2_handle in the jbd2_journal_stop function while i_data_sem is locked. This triggers lockdep because the jbd2_journal_start function might also lock the same jbd2_handle simultaneously. Found by Linux Verification Center (linuxtesting.org) with syzkaller. Rule: add

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Oct 21, 2024
Updated
Oct 15, 2026
EPSS
0.1% · 8th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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-50006

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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 kernelbefore 5.10.227
  • linux linux kernel5.11 and later · before 5.15.168
  • linux linux kernel5.16 and later · before 6.1.113
  • linux linux kernel6.2 and later · before 6.6.55
  • linux linux kernel6.7 and later · before 6.10.14
  • linux linux kernel6.11 and later · before 6.11.3

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

    • 3.10affected
    • e8238f9a8339b3578c85e4192a7a23bc2bdc0333 and later · before 4192adefc9c570698821c5eb9873320eac2fcbf1affected · git
    • e8238f9a8339b3578c85e4192a7a23bc2bdc0333 and later · before 3c46d6060d3e38de22196c1fe7706c5a3c696285affected · git
    • e8238f9a8339b3578c85e4192a7a23bc2bdc0333 and later · before 53b1999cfd2c7addf2e581a32865fe8835467b44affected · git
    • e8238f9a8339b3578c85e4192a7a23bc2bdc0333 and later · before ef05572da0c0eb89614ed01cc17d3c882bdbd1ffaffected · git
    • e8238f9a8339b3578c85e4192a7a23bc2bdc0333 and later · before 9fedf51ab8cf7b69bff08f37fe0989fec7f5d870affected · git
    • e8238f9a8339b3578c85e4192a7a23bc2bdc0333 and later · before d43776b907659affef1de888525847d64b244194affected · git
    • e8238f9a8339b3578c85e4192a7a23bc2bdc0333 and later · before 6252cb6bde7fc76cb8dcb49d1def7c326b190820affected · git
    • e8238f9a8339b3578c85e4192a7a23bc2bdc0333 and later · before d58a00e981d3118b91d503da263e640b7cde6729affected · git
    • e8238f9a8339b3578c85e4192a7a23bc2bdc0333 and later · before cc749e61c011c255d81b192a822db650c68b313faffected · git

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.115-16.1.115-1
Debian:13linuxbefore 6.11.4-16.11.4-1

Same product

linux: all records

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-49998Oct 21, 2024 · net: dsa: improve shutdown sequence
    18Monitor
  • ← EarlierCVE-2024-50001Oct 21, 2024 · net/mlx5: Fix error path in multi-packet WQE transmit
    22Monitor
  • Later →CVE-2024-50008Oct 21, 2024 · wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext()
    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 Linux3c46d6060d3e38de22196c1fe7706c5a3c696285Vendor (CNA)
Linux Linux4192adefc9c570698821c5eb9873320eac2fcbf1Vendor (CNA)
Linux Linux53b1999cfd2c7addf2e581a32865fe8835467b44Vendor (CNA)
Linux Linux6252cb6bde7fc76cb8dcb49d1def7c326b190820Vendor (CNA)
Linux Linux9fedf51ab8cf7b69bff08f37fe0989fec7f5d870Vendor (CNA)
Linux Linuxcc749e61c011c255d81b192a822db650c68b313fVendor (CNA)
Linux Linuxd43776b907659affef1de888525847d64b244194Vendor (CNA)
Linux Linuxd58a00e981d3118b91d503da263e640b7cde6729Vendor (CNA)
Linux Linuxef05572da0c0eb89614ed01cc17d3c882bdbd1ffVendor (CNA)
Azure Linux 3.0 ARM6.6.57.1-2 · kernelMicrosoft (MSRC)
Azure Linux 3.0 x646.6.57.1-2 · kernelMicrosoft (MSRC)
debian:linux6.1.115-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.

Credits

All researchers

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.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
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:H/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

Show all references (13 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records