{"api_version":"1","generated_at":"2026-09-12T12:04:55+00:00","cve":"CVE-2026-89600","urls":{"html":"https://cve.report/CVE-2026-89600","api":"https://cve.report/api/cve/CVE-2026-89600.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-89600","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-89600"},"summary":{"title":"fanotify: fix use-after-free of file range info","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfanotify: fix use-after-free of file range info\n\nfsnotify_pre_content() builds its file_range on the triggering task's\nstack. fanotify_alloc_perm_event() saves a pointer to range.pos in the\nheap-allocated permission event so copy_range_info_to_user() can report\nthe offset later.\n\nThe event reader can set the event state to FAN_EVENT_REPORTED and then\nsleep while preparing the file descriptor. If a signal interrupts the\ntriggering task at that point, fanotify_get_response() changes the state\nto FAN_EVENT_CANCELED and returns. This unwinds the file_range stack\nframe while the reader still owns the event. The reader then dereferences\npevent->ppos and copies the stale stack value to userspace.\n\nKASAN reported:\n\n  BUG: KASAN: use-after-free in fanotify_read+0x293e/0x2970\n  Read of size 8 at addr ffff88811434fc50 by task fanotify_inotif/95\n  Call Trace:\n   fanotify_read+0x293e/0x2970\n   vfs_read+0x177/0xa20\n   ksys_read+0xf7/0x1c0\n   do_syscall_64+0xf9/0x540\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nStore the range position directly in the permission event and use\nFANOTIFY_NO_RANGE when range information is unavailable. The event remains\nalive until the reader finishes, so the reported offset no longer depends\non the triggering task's stack.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-11 20:19:44","updated_at":"2026-09-11 20:19:44"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/d7f1cf5be33ef0175a4e8ed8687aeb98fb00a851","name":"https://git.kernel.org/stable/c/d7f1cf5be33ef0175a4e8ed8687aeb98fb00a851","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/66aa9a9e6481bfa512ee5b6380eaaec455a954d2","name":"https://git.kernel.org/stable/c/66aa9a9e6481bfa512ee5b6380eaaec455a954d2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b8f73b163b646bc56d4dce9c697a578e333f4894","name":"https://git.kernel.org/stable/c/b8f73b163b646bc56d4dce9c697a578e333f4894","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-89600","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89600","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 870499bc1d4dc04cba1f63dd5e7bc02b983e2458 66aa9a9e6481bfa512ee5b6380eaaec455a954d2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 870499bc1d4dc04cba1f63dd5e7bc02b983e2458 b8f73b163b646bc56d4dce9c697a578e333f4894 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 870499bc1d4dc04cba1f63dd5e7bc02b983e2458 d7f1cf5be33ef0175a4e8ed8687aeb98fb00a851 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.14","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.14 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.50 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.4 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/notify/fanotify/fanotify.c","fs/notify/fanotify/fanotify.h","fs/notify/fanotify/fanotify_user.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"66aa9a9e6481bfa512ee5b6380eaaec455a954d2","status":"affected","version":"870499bc1d4dc04cba1f63dd5e7bc02b983e2458","versionType":"git"},{"lessThan":"b8f73b163b646bc56d4dce9c697a578e333f4894","status":"affected","version":"870499bc1d4dc04cba1f63dd5e7bc02b983e2458","versionType":"git"},{"lessThan":"d7f1cf5be33ef0175a4e8ed8687aeb98fb00a851","status":"affected","version":"870499bc1d4dc04cba1f63dd5e7bc02b983e2458","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/notify/fanotify/fanotify.c","fs/notify/fanotify/fanotify.h","fs/notify/fanotify/fanotify_user.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.14"},{"lessThan":"6.14","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.50","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.50","versionStartIncluding":"6.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.4","versionStartIncluding":"6.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"6.14","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nfanotify: fix use-after-free of file range info\n\nfsnotify_pre_content() builds its file_range on the triggering task's\nstack. fanotify_alloc_perm_event() saves a pointer to range.pos in the\nheap-allocated permission event so copy_range_info_to_user() can report\nthe offset later.\n\nThe event reader can set the event state to FAN_EVENT_REPORTED and then\nsleep while preparing the file descriptor. If a signal interrupts the\ntriggering task at that point, fanotify_get_response() changes the state\nto FAN_EVENT_CANCELED and returns. This unwinds the file_range stack\nframe while the reader still owns the event. The reader then dereferences\npevent->ppos and copies the stale stack value to userspace.\n\nKASAN reported:\n\n  BUG: KASAN: use-after-free in fanotify_read+0x293e/0x2970\n  Read of size 8 at addr ffff88811434fc50 by task fanotify_inotif/95\n  Call Trace:\n   fanotify_read+0x293e/0x2970\n   vfs_read+0x177/0xa20\n   ksys_read+0xf7/0x1c0\n   do_syscall_64+0xf9/0x540\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nStore the range position directly in the permission event and use\nFANOTIFY_NO_RANGE when range information is unavailable. The event remains\nalive until the reader finishes, so the reported offset no longer depends\non the triggering task's stack."}],"providerMetadata":{"dateUpdated":"2026-09-11T19:45:03.450Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/66aa9a9e6481bfa512ee5b6380eaaec455a954d2"},{"url":"https://git.kernel.org/stable/c/b8f73b163b646bc56d4dce9c697a578e333f4894"},{"url":"https://git.kernel.org/stable/c/d7f1cf5be33ef0175a4e8ed8687aeb98fb00a851"}],"title":"fanotify: fix use-after-free of file range info","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-89600","datePublished":"2026-09-11T19:45:03.450Z","dateReserved":"2026-09-11T19:38:34.732Z","dateUpdated":"2026-09-11T19:45:03.450Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-11 20:19:44","lastModifiedDate":"2026-09-11 20:19:44","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"89600","Ordinal":"1","Title":"fanotify: fix use-after-free of file range info","CVE":"CVE-2026-89600","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"89600","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nfanotify: fix use-after-free of file range info\n\nfsnotify_pre_content() builds its file_range on the triggering task's\nstack. fanotify_alloc_perm_event() saves a pointer to range.pos in the\nheap-allocated permission event so copy_range_info_to_user() can report\nthe offset later.\n\nThe event reader can set the event state to FAN_EVENT_REPORTED and then\nsleep while preparing the file descriptor. If a signal interrupts the\ntriggering task at that point, fanotify_get_response() changes the state\nto FAN_EVENT_CANCELED and returns. This unwinds the file_range stack\nframe while the reader still owns the event. The reader then dereferences\npevent->ppos and copies the stale stack value to userspace.\n\nKASAN reported:\n\n  BUG: KASAN: use-after-free in fanotify_read+0x293e/0x2970\n  Read of size 8 at addr ffff88811434fc50 by task fanotify_inotif/95\n  Call Trace:\n   fanotify_read+0x293e/0x2970\n   vfs_read+0x177/0xa20\n   ksys_read+0xf7/0x1c0\n   do_syscall_64+0xf9/0x540\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nStore the range position directly in the permission event and use\nFANOTIFY_NO_RANGE when range information is unavailable. The event remains\nalive until the reader finishes, so the reported offset no longer depends\non the triggering task's stack.","Type":"Description","Title":"fanotify: fix use-after-free of file range info"}]}}}