Kernel memory disclosure via fan-state table overread
Published May 21, 2024 · Updated May 11, 2026
An out-of-bounds read in the Linux kernel mlxreg-fan driver allows local users to read kernel memory through a sysfs write. mlxreg_fan_set_cur_state incorrectly returns success for an enforced fan state above the normal maximum, causing thermal_cooling_device_stats_update to index beyond its statistics table. The affected path requires supported Mellanox fan hardware, write access to the cooling-state sysfs file, and CONFIG_THERMAL_STATISTICS; the resulting read can disclose memory or crash the kernel.
Summary
What happened
An out-of-bounds read in the Linux kernel mlxreg-fan driver allows local users to read kernel memory through a sysfs write. mlxreg_fan_set_cur_state incorrectly returns success for an enforced fan state above the normal maximum, causing thermal_cooling_device_stats_update to index beyond its statistics table. The affected path requires supported Mellanox fan hardware, write access to the cooling-state sysfs file, and CONFIG_THERMAL_STATISTICS; the resulting read can disclose memory or crash the kernel.
The record
- CVE
- CVE-2021-47393
- Published
- May 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.19
- Affected versionversion=65afb4c8e7e4e7e74b28efa1df62da503ca3e7a6 <5c6e0bce647d9cb32a17d58ffa669b3421fcc6ca
- Affected versionversion=65afb4c8e7e4e7e74b28efa1df62da503ca3e7a6 <76bbb482d33bfcd7e9070ecf594c9ec73e01c930
- Affected versionversion=65afb4c8e7e4e7e74b28efa1df62da503ca3e7a6 <a6c42ae1530f94724d3c42cf91fe3d3c5e394f8a
- Affected versionversion=65afb4c8e7e4e7e74b28efa1df62da503ca3e7a6 <aa85fb7bde558bb2e364e85976b14b259c8b6fe8
- Affected versionversion=65afb4c8e7e4e7e74b28efa1df62da503ca3e7a6 <e6fab7af6ba1bc77c78713a83876f60ca7a4a064
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo