Latent overflow via unchecked channel name copy
Published Feb 26, 2025 · Updated May 11, 2026
Buffer overflow in the nvidiafb I2C setup code in Linux allows attackers to cause unspecified impact via unspecified vectors. The static nvidia_setup_i2c_bus() function copies its name parameter into the 48-byte chan->adapter.name buffer with strcpy() and no length check. Linux kernel maintainers found no existing call site capable of supplying an overlong name, so the flawed copy is latent and no present exploit path or consequence is established.
Summary
What happened
Buffer overflow in the nvidiafb I2C setup code in Linux allows attackers to cause unspecified impact via unspecified vectors. The static nvidia_setup_i2c_bus() function copies its name parameter into the 48-byte chan->adapter.name buffer with strcpy() and no length check. Linux kernel maintainers found no existing call site capable of supplying an overlong name, so the flawed copy is latent and no present exploit path or consequence is established.
The record
- CVE
- CVE-2021-47642
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <055cdd2e7b992921424d4daaa285ced787fb205f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <08dff482012758935c185532b1ad7d584785a86e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <37a1a2e6eeeb101285cd34e12e48a881524701aa
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <41baa86b6c802cdc6ab8ff2d46c083c9be93de81
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <47e5533adf118afaf06d25a3e2aaaab89371b1c5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <580e5d3815474b8349250c25c16416585a72c7fe
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6a5226e544ac043bb2d8dc1bfe8920d02282f7cd
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <72dd5c46a152136712a55bf026a9aa8c1b12b60d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9ff2f7294ab0f011cd4d1b7dcd9a07d8fdf72834
- Affected versionversion=2.6.12
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
No sourced classifications are available.
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