PatchSiren cyber security CVE debrief
CVE-2026-64159 Linux CVE debrief
The Linux kernel was vulnerable to an issue in the netfs module, which could allow for incorrect updates to the zero point in netfs_release_folio() when there is uncommitted data in the pagecache beyond the folio being released but the on-server EOF is in this folio. This could lead to read-gaps on folio failing with a short read if the FMODE_READ check is commented out in netfs_perform_write(). The fix applied correctly updates the zero point by limiting zero_point to remote_i_size, not i_size.
- Vendor
- Linux
- Product
- Unknown
- CVSS
- Unknown
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-19
- Original CVE updated
- 2026-07-19
- Advisory published
- 2026-07-19
- Advisory updated
- 2026-07-19
Who should care
Users of Linux kernel with uncommitted data in the pagecache beyond the folio being released but the on-server EOF is in this folio should be aware of this vulnerability and take necessary actions to protect their systems.
Technical summary
The Linux kernel was vulnerable to an issue in the netfs module. A fix was applied to correctly update the zero point in netfs_release_folio() when there is uncommitted data in the pagecache beyond the folio being released but the on-server EOF is in this folio. The update needs to limit zero_point to remote_i_size, not i_size as i_size is a local phenomenon reflecting updates made locally to the pagecache, not stuff written to the server. remote_i_size tracks the server's i_size. This fix prevents read-gaps on folio failing with a short read.
Defensive priority
Medium
Recommended defensive actions
- Apply the fix to update the zero point in netfs_release_folio()
- Limit zero_point to remote_i_size, not i_size
- Monitor for uncommitted data in the pagecache beyond the folio being released but the on-server EOF is in this folio
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record was published on 2026-07-19T16:17:57.913Z and has not been modified since then. The NVD entry is currently Received. There is limited information available about the vulnerability, and defenders should verify the affected scope and severity with the official advisory.
Official resources
-
CVE-2026-64159 CVE record
CVE.org
-
CVE-2026-64159 NVD detail
NVD
-
Source item URL
nvd_modified
-
Source reference
416baaa9-dc9f-4396-8d5f-8c081fb06d67
-
Source reference
416baaa9-dc9f-4396-8d5f-8c081fb06d67
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-07-19T16:17:57.913Z and has not been modified since then. The NVD entry is currently Received.