PatchTheCVECVE-2021-42257: check_smart before 6.9.1 allows unintended drive access by an unprivileged user because it only checks for a s
CVE-2021-42257 is a high-severity flaw (CVSS 7.1) affecting check smart. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
check_smart before 6.9.1 allows unintended drive access by an unprivileged user because it only checks for a substring match of a device path (the /dev/bus substring and a number), aka an unanchored regular expression.
Why this priority
- High severity
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.1 (High) |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.4% (top 67%) |
| CISA exploited list | No |
| Weakness | CWE-20 |
| Published | 2021-10-11 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2021-42257?
check smart: upgrade to 6.9.1. Exact commands for each OS are on this page.
Is CVE-2021-42257 being exploited?
CVE-2021-42257 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2021-42257 affect?
CVE-2021-42257 affects check smart. Severity is high (CVSS 7.1). check_smart before 6.9.1 allows unintended drive access by an unprivileged user because it only checks for a substring match of a device path (the /dev/bus substring and a number), aka an unanchored regular expression.
How urgent is CVE-2021-42257?
Priority 38/100. High severity; Public exploit reference