Security readout for executives and security teams
Plain-English summary
A Linux kernel reference-counting flaw can free memory while it is still in use during certain file reads. The reported failure occurred with an EROFS file-backed mount over v9fs in QEMU. Successful triggering could crash the system or corrupt sensitive kernel memory; the supplied CVSS assessment also allows confidentiality and integrity impact.
Executive priority
Treat this as a high-priority kernel update for exposed virtualization and file-serving systems. Schedule remediation promptly, while prioritizing hosts that permit untrusted local users or use v9fs with EROFS. Emergency incident response is not justified solely by the supplied evidence because active exploitation has not been established.
Technical view
Pages in a bvec may be coalesced across a folio boundary without incrementing every non-slab folio reference count. When p9_release_pages later drops those references, a folio can be released prematurely, causing a use-after-free and bad-page state. The kernel fix increases the required folio reference counts.
Likely exposure
Prioritize systems using the listed affected Linux 6.14 through 6.15 versions, especially virtualization or file-serving workloads combining v9fs with EROFS-backed reads. The bundle identifies a specific observed configuration, but does not establish that every listed kernel installation is practically triggerable.
Exploitation context
The supplied CVSS 3.1 vector is 7.8 and requires local access with low privileges, low complexity, and no user interaction. CISA KEV status is false, and the sources provide no evidence of active exploitation or a public exploit. Practical reliability and impact beyond the reported use-after-free remain unclear.
Researcher notes
The observed fault path runs from EROFS readahead through v9fs zero-copy reads to p9_release_pages. The root issue is incomplete reference acquisition when bvec entries cross folio boundaries. The bundle names two stable commits but does not provide complete distribution package mappings, exploitability analysis, or evidence that the reported configuration covers every possible trigger.
Mitigation direction
- Update to a vendor-supported kernel containing the referenced stable fix commits.
- Check distribution advisories to identify the exact fixed package for each operating system.
- Where updating is delayed, restrict untrusted local access to systems using the affected storage configuration.
- Consider avoiding the implicated EROFS-over-v9fs workflow until vendor remediation is applied.
Validation and detection
- Inventory running kernel versions and identify systems within the supplied affected 6.14-to-6.15 range.
- Identify hosts using v9fs, particularly EROFS file-backed mounts in virtualized environments.
- Confirm installed kernel packages include the applicable referenced stable fix.
- Review kernel logs for bad-page reports, folio warnings, or traces involving p9_release_pages.
- Reboot after updating and verify the remediated kernel is running.
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-2025-37779 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/d833f21162c4d536d729628f8cf1ee8d4110f2b7CVE reference, Linux
- https://git.kernel.org/stable/c/770c8d55c42868239c748a3ebc57c9e37755f842CVE 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.