Cyber Resilience

CVE-2024-27021

Linux Kernel 6.8 – 6.8.8

Published
01 May 2024
Modified
04 November 2025
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0018 8th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2024-27021 is a high-severity Improper Locking (CWE-667) vulnerability in Linux Linux Kernel. Its CVSS base score is 7.8 (High).

Operationally, ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

In the Linux kernel, the following vulnerability has been resolved: r8169: fix LED-related deadlock on module removal Binding devm_led_classdev_register() to the netdev is problematic because on module removal we get a RTNL-related deadlock. Fix this by avoiding the device-managed LED…

more

functions. Note: We can safely call led_classdev_unregister() for a LED even if registering it failed, because led_classdev_unregister() detects this and is a no-op in this case.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-27014Same product: Fedoraproject Fedora
CVE-2024-26987Same product: Fedoraproject Fedora
CVE-2023-0160Same product: Fedoraproject Fedora
CVE-2024-27016Same product: Fedoraproject Fedora
CVE-2023-39197Same product: Fedoraproject Fedora
CVE-2023-3106Same product: Fedoraproject Fedora
CVE-2023-5345Same product: Fedoraproject Fedora
CVE-2024-27400Same product: Fedoraproject Fedora
CVE-2024-27017Same product: Fedoraproject Fedora
CVE-2023-5972Same product: Fedoraproject Fedora

Affected Assets

linux
linux kernel
6.9 · 6.8 — 6.8.8
fedoraproject
fedora
38, 39, 40

Mitigating Controls

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly include code reviews, static analysis, and concurrency standards that prevent improper locking.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Security testing can detect race conditions and locking errors before release.

prevents

Secure development lifecycle includes concurrency and locking requirements that reduce improper locking defects.

prevents

Application security requirements can mandate proper lock acquisition/release patterns.

prevents

Secure architecture principles address thread-safety and resource synchronization.

prevents

Secure coding standards directly prohibit missing or incorrect lock usage.

prevents

Change management may catch locking issues introduced by modifications but does not prevent the weakness itself.

References