CVE-2024-58069
rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read The nvmem interface supports variable buffer sizes, while the regmap interface operates with fixed-size storage. If an nvmem client uses a buffer size less than 4 bytes, regmap_read will write out of bounds as it expects the buffer to point at an unsigned int. Fix this by using an intermediary unsigned int to hold the value.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.2
References 8
git.kernel.org
- stable/c/21cd59fcb9952eb7505da2bdfc1eb9c619df3ff4
- stable/c/6f2a8ca9a0a38589f52a7f0fb9425b9ba987ae7c
- stable/c/e5536677da803ed54a29a446515c28dce7d3d574
- stable/c/c72b7a474d3f445bf0c5bcf8ffed332c78eb28a1
- stable/c/9adefa7b9559d0f21034a5d5ec1b55840c9348b9
- stable/c/e5e06455760f2995b16a176033909347929d1128
- stable/c/517aedb365f2c94e2d7e0b908ac7127df76203a1
- stable/c/3ab8c5ed4f84fa20cd16794fe8dc31f633fbc70c