Security readout for executives and security teams
Plain-English summary
A flaw in Linux performance-monitoring code can read beyond the intended memory object when hardware and software events appear together during automatic counter reload. A local, low-privileged user may be able to trigger serious confidentiality, integrity, or availability effects. The supplied evidence does not establish remote reachability or exploitation in the wild.
Executive priority
Treat as a high-priority local privilege-boundary risk. Accelerate remediation on shared compute, developer platforms, and systems running untrusted workloads. Internet exposure alone does not create the stated attack path, so prioritize according to local-user access and perf availability rather than external network reachability.
Technical view
The x86 Intel PMU path could treat a software-event PMU as an x86 hybrid PMU. A container_of operation reached through intel_pmu_set_acr_caused_constr could then perform out-of-bounds reads. The kernel fix guards that call with is_x86_event. CVSS 3.1 is 7.8: local, low-complexity, low-privilege, no user interaction.
Likely exposure
Exposure is most likely on Intel x86 Linux systems running affected kernel releases where low-privileged local users can exercise relevant perf event functionality. The bundle lists 6.16, 6.18.22, 6.19.12, and 7.0 as affected, but also contains an ambiguous “0” entry; confirm exact distribution kernel status with its vendor.
Exploitation context
The supplied CVSS vector describes a local, low-privilege attack path, not a remote one. The record is not in KEV, and the supplied sources provide no evidence of active exploitation, public proof-of-concept availability, or demonstrated impact beyond the potential out-of-bounds reads and scored security consequences.
Researcher notes
The vulnerable condition combines auto counter reload groups with software events. The PMU type mismatch makes the hybrid helper’s container conversion unsafe; the stated correction adds an is_x86_event check before intel_pmu_set_acr_caused_constr. No CWE, crash trace, exploit demonstration, or precise upstream introduction-to-fix ranges are supplied. The repeated ec980e4 commit entries and unusual affected “0” warrant vendor confirmation.
Mitigation direction
- Apply the vendor-supported kernel update containing the applicable referenced stable fix.
- Confirm distribution advisories because backported fixes may not match upstream version numbers.
- Prioritize multi-user, shared-hosting, and other systems permitting untrusted local access.
- Review vendor guidance for temporary restrictions if immediate kernel updating is impossible.
Validation and detection
- Record each system’s architecture, kernel release, distribution package version, and update status.
- Check whether the installed kernel includes an applicable referenced stable commit or vendor backport.
- Identify systems allowing untrusted local users or workloads to access perf functionality.
- After updating, reboot into the corrected kernel and verify the active kernel package.
- Monitor vendor advisories for clarified affected ranges and additional stable fixes.
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-31782 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/e435a30ca6fe14c9611b1fc731c98a6d28410247CVE reference, Linux
- https://git.kernel.org/stable/c/bfee04838f636d064bc92075c65c95f739003804CVE reference, Linux
- https://git.kernel.org/stable/c/dbde07f06226438cd2cf1179745fa1bec5d8914aCVE 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.