Security readout for executives and security teams
Plain-English summary
A Linux kernel RTC driver bug can let a local, low-privileged user trigger an out-of-bounds write when the PCF85063 NVMEM read path handles a buffer smaller than four bytes. Impact is rated high because kernel memory corruption can threaten confidentiality, integrity, and availability, but the sources do not show remote exploitation.
Executive priority
Treat as a high-priority kernel maintenance item where affected Linux kernels and local user access exist. It is not presented as internet-exploitable or actively exploited in the provided sources, so prioritize patching based on asset criticality, shared access, and whether the PCF85063 RTC driver is used.
Technical view
The pcf85063 RTC NVMEM read path passed a caller-sized buffer to regmap_read, which writes as if the destination is an unsigned int. If the NVMEM client buffer is under four bytes, regmap_read can write beyond bounds. The upstream fix stores the value in an intermediate unsigned int before copying appropriately.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions with the PCF85063 RTC driver/NVMEM interface reachable by local users or local services. The CVSS vector requires local access and low privileges. The provided sources do not establish exposure for systems without this driver path.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation. The vulnerability is local, low-complexity, and needs privileges, with no user interaction. Practical risk depends on whether local users or compromised local processes can reach the affected NVMEM read path.
Researcher notes
Evidence is limited to the CVE description, Linux stable commit references, CVSS, and Debian LTS advisories. The root cause is a size mismatch between variable-length NVMEM buffers and regmap_read fixed unsigned-int storage. No public exploit, proof-of-concept, or non-kernel product impact is cited in the bundle.
Mitigation direction
- Update to a vendor kernel containing the listed Linux stable fixes.
- For Debian LTS systems, review the cited Debian advisories and apply kernel updates.
- Check vendor guidance for supported fixed versions before deploying custom kernel changes.
- Prioritize multi-user, shared, embedded, or appliance systems using the PCF85063 driver.
Validation and detection
- Inventory Linux kernel versions against the affected versions in the CVE record.
- Confirm whether the PCF85063 RTC driver and NVMEM interface are present or enabled.
- Verify installed kernel packages include the relevant stable commit fixes.
- Review local access paths and services that could trigger NVMEM reads.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-787: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-58069 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/21cd59fcb9952eb7505da2bdfc1eb9c619df3ff4CVE reference, Linux
- https://git.kernel.org/stable/c/6f2a8ca9a0a38589f52a7f0fb9425b9ba987ae7cCVE reference, Linux
- https://git.kernel.org/stable/c/e5536677da803ed54a29a446515c28dce7d3d574CVE reference, Linux
- https://git.kernel.org/stable/c/c72b7a474d3f445bf0c5bcf8ffed332c78eb28a1CVE reference, Linux
- https://git.kernel.org/stable/c/9adefa7b9559d0f21034a5d5ec1b55840c9348b9CVE reference, Linux
- https://git.kernel.org/stable/c/e5e06455760f2995b16a176033909347929d1128CVE reference, Linux
- https://git.kernel.org/stable/c/517aedb365f2c94e2d7e0b908ac7127df76203a1CVE reference, Linux
- https://git.kernel.org/stable/c/3ab8c5ed4f84fa20cd16794fe8dc31f633fbc70cCVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/05/msg00030.htmlCVE reference, CVE
- https://lists.debian.org/debian-lts-announce/2025/03/msg00028.htmlCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.