CVE-2017-18203: Race Condition

Published Feb 27, 2018
·
Updated

Last updated 4 July 2026

Other sources

The dmgetfromkobject function in drivers/md/dm.c in the Linux kernel before 4.14.3 allow local users to cause a denial of service (BUG) by leveraging a race condition with dmdestroy during creation and removal of DM devices.

Launchpad

The Linux kernel before version 4.14.3 is vulnerable to a denial of service in drivers/md/dm.c:dmgetfromkobject() which can be caused by local users leveraging a race condition with dmdestroy() during creation and removal of DM devices. Only privileged local users (with CAPSYSADMIN capability) can directly perform the ioctl operations for dm device creation and removal and this would typically be outside the direct control of the unprivileged attacker.

References:

https://patchwork.kernel.org/patch/10035971/

https://marc.info/?l=dm-devel&m=150952182422209&w=2

An upstream commit:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b9a41d21dceadf8104812626ef85dc56ee8a60ed

Red Hat

Affected Software

3 affected componentsFixes available
redhat/kernel<4.14.3
4.14.3
Linux Linux kernel<4.14.3
debian/linux
5.10.223-15.10.262-16.1.176-16.1.180-16.12.94-16.12.101-17.1.8-17.1.8-2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/kernel to a version that resolves this vulnerability.

    Fixed in 4.14.3
  2. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.262-1Fixed in 6.1.176-1Fixed in 6.1.180-1Fixed in 6.12.94-1Fixed in 6.12.101-1Fixed in 7.1.8-1Fixed in 7.1.8-2
  3. Upgrade

    Upgrade linux kernel to a version that resolves this vulnerability.

    Fixed in 4.14.3
  4. Compensating control

    Mitigate by restricting who can create/remove device-mapper (dm) devices so only privileged local users with CAP_SYS_ADMIN can perform the dm device creation and removal ioctl operations.

Event History

Feb 27, 2018
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
Description
Data Sourced
via NVD·08:29 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 11, 2024
Data Sourced
via Launchpad·10:35 PM
Description
Jul 5, 2026
Data Sourced
via Ubuntu·11:12 AM
RemedyDescriptionSeverityAffected Software
Aug 16, 2026
Data Sourced
via Debian·12:40 PM
DescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2017-18203?

CVE-2017-18203 has been classified as a high-severity vulnerability due to its potential to cause denial of service.

2

How do I fix CVE-2017-18203?

To fix CVE-2017-18203, update the Linux kernel to version 4.14.3 or later.

3

Which versions of the Linux kernel are affected by CVE-2017-18203?

CVE-2017-18203 affects Linux kernel versions prior to 4.14.3.

4

Is there a patch available for CVE-2017-18203?

Yes, a patch is available in Linux kernel version 4.14.3 and subsequent releases.

5

What impact does CVE-2017-18203 have on system security?

CVE-2017-18203 can lead to denial of service, compromising system availability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203