netfs: zero gaps in read-gaps folio to avoid writing back stale data
CVSS score
—
EPSS probability
—
Risk score
—
Published
8 h ago
Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.
Impact on My Inventory
Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.
Checking session…
Vulnerability description
CVE AI research
DayBreach AI Explanation
Verified against sourcesSources read
1
Source agreement
Tam uyum
Evidence confidence
%55
Short explanation
A vulnerability was identified in the Linux kernel netfs subsystem where gaps around streaming write regions were left unread on the server side, causing stale folio contents to be written back (S0). The netfs_read_gaps() function has been adjusted to zero out the shortfall after the read completes instead of before (S0).
This issue can lead to stale folio data being written back due to short or EOF responses from the server side (S0). Addressing this kernel-level data integrity flaw helps prevent unexpected data corruption scenarios (S0).
What should be done?
- Applying relevant Linux kernel updates
- Following vendor advisories and upstream git commits
- Reviewing the netfs_read_gaps patching logic in the kernel source
Chain of evidence and sources
netfs_read_gaps() fonksiyonu, streaming yazma işlemlerindeki kirli bölge etrafındaki boşlukları sunucu tarafında okunmamış bırakmaktadır.
Kısa veya EOF yanıtları, daha sonradan geri yazılan bayat folio içeriklerinin kalmasına neden olmaktadır.
Çözüm olarak, okuma tamamlandıktan sonra aynı bvec dizisi üzerinde bir yineleyici oluşturularak kalan kısım sıfırlanmaktadır.
Show the technical text from the sources
In the Linux kernel, the following vulnerability has been resolved: netfs: zero gaps in read-gaps folio to avoid writing back stale data netfs_read_gaps() leaves gaps around a streaming write's dirty region unread on the server side, so a short/EOF response there left stale folio content that later got written back. Zero it after the read completes, not before: netfs_wait_for_read() returns rreq->transferred once ret >= 0, so build an iterator over the same bvec array the read used, advance past ret, and zero the rest. The dirty region already maps to sink pages in that array rather than the real folio, so this can't touch it, and only the actual shortfall gets zeroed instead of the whole gap upfront.
Explanation produced with the local gemini-flash-lite-latest model. Numerical metrics and the KEV, patch and exploit statuses are not determined by AI.
IMPACT: Affected Products and Software
RED HAT CSAF/VEX: Product Impact Check
SCORING: CVSS from Multiple Sources
CVSS Scores
The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.
| SCORE | VERSION | SEVERITY | VECTOR | SOURCE |
|---|---|---|---|---|
| The sources have not yet published a verified CVSS metric. | ||||
Patch and Remediation Guide
Solution & Remediation Advisory
İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.
Public exploit and active exploitation status
Verified exploit intelligence
No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.
Weakness Classification and Attack Patterns (CWE & CAPEC)
CWE - Common Weakness Enumeration
While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-98843 is associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-98843 weaknesses.
Official Sources and Advisories
Yama durumu bilinmiyor
Similar Vulnerabilities
Get this vulnerability through the API
Affected products, version ranges, exploitation status and patch information in a single request, with a free key.
curl -H "x-api-key: $DAYBREACH_API_KEY" \ "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-98843"