{"api_version":"1","generated_at":"2026-07-24T21:06:41+00:00","cve":"CVE-2026-64062","urls":{"html":"https://cve.report/CVE-2026-64062","api":"https://cve.report/api/cve/CVE-2026-64062.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-64062","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-64062"},"summary":{"title":"netfs: Fix potential deadlock in write-through mode","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfs: Fix potential deadlock in write-through mode\n\nFix netfs_advance_writethrough() to always unlock the supplied folio and to\nmark it dirty if it isn't yet written to the end.  Unfortunately, it can't\nbe marked for writeback until the folio is done with as that may cause a\ndeadlock against mmapped reads and writes.\n\nEven though it has been marked dirty, premature writeback can't occur as\nthe caller is holding both inode->i_rwsem (which will prevent concurrent\ntruncation, fallocation, DIO and other writes) and ictx->wb_lock (which\nwill cause flushing to wait and writeback to skip or wait).\n\nNote that this may be easier to deal with once the queuing of folios is\nsplit from the generation of subrequests.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-07-19 16:17:46","updated_at":"2026-07-19 16:17:46"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/b6a4ae1634b3ad2aaa05222e53d36da532852faf","name":"https://git.kernel.org/stable/c/b6a4ae1634b3ad2aaa05222e53d36da532852faf","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/003aa0dd26c964025acd6d1213bcdbd674db2ca9","name":"https://git.kernel.org/stable/c/003aa0dd26c964025acd6d1213bcdbd674db2ca9","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/1468f39243ccb155b6d97f9a9932f610d1205d75","name":"https://git.kernel.org/stable/c/1468f39243ccb155b6d97f9a9932f610d1205d75","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/e40e9cbf3ee4d30ee9a97bd128c85500b6ad0da1","name":"https://git.kernel.org/stable/c/e40e9cbf3ee4d30ee9a97bd128c85500b6ad0da1","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-64062","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64062","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 288ace2f57c9d06dd2e42bd80d03747d879a4068 1468f39243ccb155b6d97f9a9932f610d1205d75 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 288ace2f57c9d06dd2e42bd80d03747d879a4068 003aa0dd26c964025acd6d1213bcdbd674db2ca9 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 288ace2f57c9d06dd2e42bd80d03747d879a4068 e40e9cbf3ee4d30ee9a97bd128c85500b6ad0da1 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 288ace2f57c9d06dd2e42bd80d03747d879a4068 b6a4ae1634b3ad2aaa05222e53d36da532852faf git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.10","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.10 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.92 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.34 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.11 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"64062","cve":"CVE-2026-64062","epss":"0.001680000","percentile":"0.063780000","score_date":"2026-07-20","updated_at":"2026-07-21 00:13:14"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/netfs/write_issue.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"1468f39243ccb155b6d97f9a9932f610d1205d75","status":"affected","version":"288ace2f57c9d06dd2e42bd80d03747d879a4068","versionType":"git"},{"lessThan":"003aa0dd26c964025acd6d1213bcdbd674db2ca9","status":"affected","version":"288ace2f57c9d06dd2e42bd80d03747d879a4068","versionType":"git"},{"lessThan":"e40e9cbf3ee4d30ee9a97bd128c85500b6ad0da1","status":"affected","version":"288ace2f57c9d06dd2e42bd80d03747d879a4068","versionType":"git"},{"lessThan":"b6a4ae1634b3ad2aaa05222e53d36da532852faf","status":"affected","version":"288ace2f57c9d06dd2e42bd80d03747d879a4068","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/netfs/write_issue.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.10"},{"lessThan":"6.10","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.92","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.34","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.11","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.92","versionStartIncluding":"6.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.34","versionStartIncluding":"6.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.11","versionStartIncluding":"6.10","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1","versionStartIncluding":"6.10","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfs: Fix potential deadlock in write-through mode\n\nFix netfs_advance_writethrough() to always unlock the supplied folio and to\nmark it dirty if it isn't yet written to the end.  Unfortunately, it can't\nbe marked for writeback until the folio is done with as that may cause a\ndeadlock against mmapped reads and writes.\n\nEven though it has been marked dirty, premature writeback can't occur as\nthe caller is holding both inode->i_rwsem (which will prevent concurrent\ntruncation, fallocation, DIO and other writes) and ictx->wb_lock (which\nwill cause flushing to wait and writeback to skip or wait).\n\nNote that this may be easier to deal with once the queuing of folios is\nsplit from the generation of subrequests."}],"providerMetadata":{"dateUpdated":"2026-07-19T15:39:41.523Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/1468f39243ccb155b6d97f9a9932f610d1205d75"},{"url":"https://git.kernel.org/stable/c/003aa0dd26c964025acd6d1213bcdbd674db2ca9"},{"url":"https://git.kernel.org/stable/c/e40e9cbf3ee4d30ee9a97bd128c85500b6ad0da1"},{"url":"https://git.kernel.org/stable/c/b6a4ae1634b3ad2aaa05222e53d36da532852faf"}],"title":"netfs: Fix potential deadlock in write-through mode","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-64062","datePublished":"2026-07-19T15:39:41.523Z","dateReserved":"2026-07-19T07:54:57.030Z","dateUpdated":"2026-07-19T15:39:41.523Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-07-19 16:17:46","lastModifiedDate":"2026-07-19 16:17:46","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"64062","Ordinal":"1","Title":"netfs: Fix potential deadlock in write-through mode","CVE":"CVE-2026-64062","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"64062","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nnetfs: Fix potential deadlock in write-through mode\n\nFix netfs_advance_writethrough() to always unlock the supplied folio and to\nmark it dirty if it isn't yet written to the end.  Unfortunately, it can't\nbe marked for writeback until the folio is done with as that may cause a\ndeadlock against mmapped reads and writes.\n\nEven though it has been marked dirty, premature writeback can't occur as\nthe caller is holding both inode->i_rwsem (which will prevent concurrent\ntruncation, fallocation, DIO and other writes) and ictx->wb_lock (which\nwill cause flushing to wait and writeback to skip or wait).\n\nNote that this may be easier to deal with once the queuing of folios is\nsplit from the generation of subrequests.","Type":"Description","Title":"netfs: Fix potential deadlock in write-through mode"}]}}}