{"api_version":"1","generated_at":"2026-08-15T08:45:46+00:00","cve":"CVE-2026-74354","urls":{"html":"https://cve.report/CVE-2026-74354","api":"https://cve.report/api/cve/CVE-2026-74354.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-74354","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-74354"},"summary":{"title":"bpf: Take mmap_lock in zap_pages()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Take mmap_lock in zap_pages()\n\nzap_vma_range() requires the owning mm's mmap_lock to be held.\n\nTaking mmap_read_lock under arena->lock would AB-BA against\narena_vm_close() and arena_map_mmap(), both of which run with\nmmap_write_lock held and then acquire arena->lock. Instead drop\narena->lock, mmget_not_zero() the vma's mm, take mmap_read_lock, and\nre-resolve the vma via find_vma() since it may have been unmapped or\nreplaced while waiting.\n\nTrack processed vmls with a per-call generation in vml->zap_gen and\nserialize zap_pages() callers with a new arena->zap_mutex so\nconcurrent callers on different uaddr ranges do not mark each other's\nvmls processed before the zap is done.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 06:22:36","updated_at":"2026-08-15 06:22:36"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/36b1d997866f6083d33934983aa2ce0a184ed642","name":"https://git.kernel.org/stable/c/36b1d997866f6083d33934983aa2ce0a184ed642","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/80b89d0226a05e8b67969de99c31b51fcd54f76a","name":"https://git.kernel.org/stable/c/80b89d0226a05e8b67969de99c31b51fcd54f76a","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-74354","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74354","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 317460317a02a1af512697e6e964298dedd8a163 36b1d997866f6083d33934983aa2ce0a184ed642 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 317460317a02a1af512697e6e964298dedd8a163 80b89d0226a05e8b67969de99c31b51fcd54f76a git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.9","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.9 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.5 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-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":["kernel/bpf/arena.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"36b1d997866f6083d33934983aa2ce0a184ed642","status":"affected","version":"317460317a02a1af512697e6e964298dedd8a163","versionType":"git"},{"lessThan":"80b89d0226a05e8b67969de99c31b51fcd54f76a","status":"affected","version":"317460317a02a1af512697e6e964298dedd8a163","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["kernel/bpf/arena.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.9"},{"lessThan":"6.9","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.5","versionStartIncluding":"6.9","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc1","versionStartIncluding":"6.9","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Take mmap_lock in zap_pages()\n\nzap_vma_range() requires the owning mm's mmap_lock to be held.\n\nTaking mmap_read_lock under arena->lock would AB-BA against\narena_vm_close() and arena_map_mmap(), both of which run with\nmmap_write_lock held and then acquire arena->lock. Instead drop\narena->lock, mmget_not_zero() the vma's mm, take mmap_read_lock, and\nre-resolve the vma via find_vma() since it may have been unmapped or\nreplaced while waiting.\n\nTrack processed vmls with a per-call generation in vml->zap_gen and\nserialize zap_pages() callers with a new arena->zap_mutex so\nconcurrent callers on different uaddr ranges do not mark each other's\nvmls processed before the zap is done."}],"providerMetadata":{"dateUpdated":"2026-08-15T05:58:40.067Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/36b1d997866f6083d33934983aa2ce0a184ed642"},{"url":"https://git.kernel.org/stable/c/80b89d0226a05e8b67969de99c31b51fcd54f76a"}],"title":"bpf: Take mmap_lock in zap_pages()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-74354","datePublished":"2026-08-15T05:58:40.067Z","dateReserved":"2026-08-15T05:44:03.887Z","dateUpdated":"2026-08-15T05:58:40.067Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-15 06:22:36","lastModifiedDate":"2026-08-15 06:22:36","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"74354","Ordinal":"1","Title":"bpf: Take mmap_lock in zap_pages()","CVE":"CVE-2026-74354","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"74354","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Take mmap_lock in zap_pages()\n\nzap_vma_range() requires the owning mm's mmap_lock to be held.\n\nTaking mmap_read_lock under arena->lock would AB-BA against\narena_vm_close() and arena_map_mmap(), both of which run with\nmmap_write_lock held and then acquire arena->lock. Instead drop\narena->lock, mmget_not_zero() the vma's mm, take mmap_read_lock, and\nre-resolve the vma via find_vma() since it may have been unmapped or\nreplaced while waiting.\n\nTrack processed vmls with a per-call generation in vml->zap_gen and\nserialize zap_pages() callers with a new arena->zap_mutex so\nconcurrent callers on different uaddr ranges do not mark each other's\nvmls processed before the zap is done.","Type":"Description","Title":"bpf: Take mmap_lock in zap_pages()"}]}}}