Skip to main content
VulnerabilityPublished Updated

CVE-2024-50014: Linux kernel · ext4: fix access to uninitialised lock in fc replay path

Affects Linux kernelSource GCVE Database

0
Compare

Not known to be exploited.

Data as of 10 Nov 2026, 14:49 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

AI-suggested

A fix is available that initializes the spinlock earlier in the ext4 filesystem code. Users should apply the updated Linux kernel version containing this fix. No additional mitigation steps are indicated or required.

Description

A vulnerability in the Linux kernel ext4 filesystem code involves accessing an uninitialized spinlock during the fast-commit replay path. This occurs in the function ext4_check_bdev_write_error() where the spinlock sbi->s_bdev_wb_lock is used before it is initialized, potentially causing kernel warnings or instability. The issue is fixed by initializing the lock earlier in the __ext4_fill_super() function.

References

Community reviews

Loading reviews…