CVE-2021-20269: A flaw was found in the permissions of a log file created by kexec-tools.
Noroxi assessment
Priority: Monitor (action score 22/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.25% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: kexec-tools (Red Hat:enterprise_linux:8::baseos) 0:2.0.20-57.el8; kexec-tools-debuginfo (Red Hat:enterprise_linux:8::baseos) 0:2.0.20-57.el8; kexec-tools-debugsource (Red Hat:enterprise_linux:8::baseos) 0:2.0.20-57.el8.
Low priority for now. Upgrade to kexec-tools (Red Hat:enterprise_linux:8::baseos) 0:2.0.20-57.el8; kexec-tools-debuginfo (Red Hat:enterprise_linux:8::baseos) 0:2.0.20-57.el8; kexec-tools-debugsource (Red Hat:enterprise_linux:8::baseos) 0:2.0.20-57.el8 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
A flaw was found in the permissions of a log file created by kexec-tools. This flaw allows a local unprivileged user to read this file and leak kernel internal information from a previous panic. The highest threat from this vulnerability is to confidentiality. This flaw affects kexec-tools shipped by Fedora versions prior to 2.0.21-8 and RHEL versions prior to 2.0.20-47.
- Published
- Mar 10, 2022
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-276
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| kexec-tools project | kexec-tools | cpe:2.3:a:kexec-tools_project:kexec-tools |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a kexec-tools
- Fedora kexec-tools versions prior to 2.0.21-8 and RHEL kexec-tools versions prior to 2.0.20-47affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- kexec-tools project kexec-toolsbefore 2.0.21-8
- kexec-tools project kexec-toolsbefore 2.0.20-47
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:enterprise_linux:8::baseos | kexec-tools | before 0:2.0.20-57.el8 | 0:2.0.20-57.el8 |
| Red Hat:enterprise_linux:8::baseos | kexec-tools-debuginfo | before 0:2.0.20-57.el8 | 0:2.0.20-57.el8 |
| Red Hat:enterprise_linux:8::baseos | kexec-tools-debugsource | before 0:2.0.20-57.el8 | 0:2.0.20-57.el8 |
| Rocky Linux:8 | kexec-tools | before 0:2.0.20-57.el8 | 0:2.0.20-57.el8 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:kexec-tools | 0:2.0.20-57.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kexec-tools-debuginfo | 0:2.0.20-57.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kexec-tools-debugsource | 0:2.0.20-57.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| rocky linux:kexec-tools | 0:2.0.20-57.el8 · Rocky Linux:8 | Package 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-276 · Incorrect Default PermissionsCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
Attack patterns (CAPEC)
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.