Security readout for executives and security teams
Plain-English summary
A Linux kernel driver can allocate and copy the wrong amount of memory during DMA operations, potentially corrupting kernel memory. Successful abuse requires local, low-privileged access according to the supplied CVSS vector. Impact could include system compromise or disruption, but only systems using the affected ZynqMP NVMEM driver are likely relevant.
Executive priority
Treat as a high-priority kernel maintenance issue for systems using the affected driver, especially multi-user or sensitive devices. It is not currently supported as an emergency internet-wide threat because exploitation is local and active abuse is not evidenced. Establish exposure quickly, then deploy vendor-tested fixes through the normal expedited patch process.
Technical view
The zynqmp_nvmem driver used an incorrect buffer size for coherent DMA allocation and memcpy operations. This could cause access beyond an undersized DMA buffer and corrupt kernel memory. The cited kernel changes correct both sizes. The supplied record assigns CVSS 3.1 score 7.8 with local, low-privileged attack requirements and high confidentiality, integrity, and availability impacts.
Likely exposure
Prioritize Linux systems where the ZynqMP NVMEM driver is present and operational. The supplied version data lists several affected releases but does not clearly define complete version intervals or fixed-release mappings. Systems without this driver are unlikely to reach the vulnerable code path, although configuration and vendor backports must be verified.
Exploitation context
The supplied record does not list this CVE in KEV and provides no evidence of active exploitation or public exploit availability. The CVSS vector describes local exploitation requiring low privileges, low complexity, and no user interaction. Whether an attacker can reliably convert the memory corruption into full compromise is not established by these sources.
Researcher notes
No CWE is supplied. The record identifies possible kernel memory corruption but does not document triggering conditions, exploit reliability, or complete version boundaries. Four stable-kernel commits are cited, likely reflecting fixes across maintained branches, but the bundle does not map each commit to a release. Avoid inferring remote reachability or confirmed privilege escalation beyond the supplied CVSS assessment.
Mitigation direction
- Update to a vendor-supported kernel containing the applicable cited fix.
- Confirm appliance and distribution vendors have backported the correction.
- Restrict local account access until affected systems are updated.
- Prioritize exposed multi-user and high-value systems using the driver.
Validation and detection
- Inventory kernels and determine whether the ZynqMP NVMEM driver is configured or loaded.
- Compare deployed kernel sources or vendor advisories against the cited fix commits.
- Verify the update corrects DMA allocation and memcpy buffer sizing.
- Run established regression testing after updating affected kernels.
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.
CVE-2026-31743 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.
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.9LinuxVulnerability 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.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/2f6e5b9964d0a63a5ba84fca2642876afb70a662CVE reference, Linux
- https://git.kernel.org/stable/c/784ed4abded1ca4b525fa4cade8b02f8c5d2a087CVE reference, Linux
- https://git.kernel.org/stable/c/6c01e7f11f5e5f22285d19510a9643e2506e13c3CVE reference, Linux
- https://git.kernel.org/stable/c/f9b88613ff402aa6fe8fd020573cb95867ae947eCVE reference, Linux
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.