{"api_version":"1","generated_at":"2026-10-02T21:36:55+00:00","cve":"CVE-2026-98039","urls":{"html":"https://cve.report/CVE-2026-98039","api":"https://cve.report/api/cve/CVE-2026-98039.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-98039","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-98039"},"summary":{"title":"bpf: Require MEM_PERCPU for percpu kptr stores","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Require MEM_PERCPU for percpu kptr stores\n\nmap_kptr_match_type() treats perm_flags as the set of register type flags\nthat a kptr field permits. Adding MEM_PERCPU to that set for\nBPF_KPTR_PERCPU does not require the source register to carry it, however.\nThe subset test consequently accepts both a plain bpf_obj_new() allocation\nand a referenced kernel pointer into a __percpu_kptr map field.\n\nLoads from the field are always marked MEM_PERCPU. Consumers then treat the\nstored value as the cookie returned by bpf_percpu_obj_new(): per-CPU pointer\nhelpers relocate it, and map teardown selects the per-CPU free path. A plain\nallocation can therefore provide an arbitrary kernel read/write, while a\nkernel pointer can be relocated into an invalid address or sent through a\nmissing destructor.\n\nRequire the source MEM_PERCPU flag to match the destination field kind.\nThis preserves valid bpf_percpu_obj_new() stores and rejects both the\nprogram-BTF and kernel-BTF variants.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-25 11:17:32","updated_at":"2026-09-25 11:17:32"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/048029ba1c793f8cabc4ad5eea765da01903f8f1","name":"https://git.kernel.org/stable/c/048029ba1c793f8cabc4ad5eea765da01903f8f1","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/0bdd6121c8dd5f1764efe701ce26bb8e15acb172","name":"https://git.kernel.org/stable/c/0bdd6121c8dd5f1764efe701ce26bb8e15acb172","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/aaa9cf7707d1c5c0d2ca9d40c8b71652ac1c3c3f","name":"https://git.kernel.org/stable/c/aaa9cf7707d1c5c0d2ca9d40c8b71652ac1c3c3f","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ad4ebae5dbc2d47b544aa54f03c12490065be08a","name":"https://git.kernel.org/stable/c/ad4ebae5dbc2d47b544aa54f03c12490065be08a","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-98039","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98039","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 36d8bdf75a93190e5669b9d1d95994e13e15ba1d aaa9cf7707d1c5c0d2ca9d40c8b71652ac1c3c3f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 36d8bdf75a93190e5669b9d1d95994e13e15ba1d 0bdd6121c8dd5f1764efe701ce26bb8e15acb172 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 36d8bdf75a93190e5669b9d1d95994e13e15ba1d ad4ebae5dbc2d47b544aa54f03c12490065be08a git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 36d8bdf75a93190e5669b9d1d95994e13e15ba1d 048029ba1c793f8cabc4ad5eea765da01903f8f1 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.7","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.7 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.111 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.53 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.7 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"98039","cve":"CVE-2026-98039","epss":"0.001680000","percentile":"0.053850000","score_date":"2026-09-27","updated_at":"2026-09-28 00:02:24"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["kernel/bpf/verifier.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"aaa9cf7707d1c5c0d2ca9d40c8b71652ac1c3c3f","status":"affected","version":"36d8bdf75a93190e5669b9d1d95994e13e15ba1d","versionType":"git"},{"lessThan":"0bdd6121c8dd5f1764efe701ce26bb8e15acb172","status":"affected","version":"36d8bdf75a93190e5669b9d1d95994e13e15ba1d","versionType":"git"},{"lessThan":"ad4ebae5dbc2d47b544aa54f03c12490065be08a","status":"affected","version":"36d8bdf75a93190e5669b9d1d95994e13e15ba1d","versionType":"git"},{"lessThan":"048029ba1c793f8cabc4ad5eea765da01903f8f1","status":"affected","version":"36d8bdf75a93190e5669b9d1d95994e13e15ba1d","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["kernel/bpf/verifier.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.7"},{"lessThan":"6.7","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.111","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.53","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.7","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.111","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.53","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.7","versionStartIncluding":"6.7","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc2","versionStartIncluding":"6.7","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Require MEM_PERCPU for percpu kptr stores\n\nmap_kptr_match_type() treats perm_flags as the set of register type flags\nthat a kptr field permits. Adding MEM_PERCPU to that set for\nBPF_KPTR_PERCPU does not require the source register to carry it, however.\nThe subset test consequently accepts both a plain bpf_obj_new() allocation\nand a referenced kernel pointer into a __percpu_kptr map field.\n\nLoads from the field are always marked MEM_PERCPU. Consumers then treat the\nstored value as the cookie returned by bpf_percpu_obj_new(): per-CPU pointer\nhelpers relocate it, and map teardown selects the per-CPU free path. A plain\nallocation can therefore provide an arbitrary kernel read/write, while a\nkernel pointer can be relocated into an invalid address or sent through a\nmissing destructor.\n\nRequire the source MEM_PERCPU flag to match the destination field kind.\nThis preserves valid bpf_percpu_obj_new() stores and rejects both the\nprogram-BTF and kernel-BTF variants."}],"providerMetadata":{"dateUpdated":"2026-09-25T10:23:52.360Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/aaa9cf7707d1c5c0d2ca9d40c8b71652ac1c3c3f"},{"url":"https://git.kernel.org/stable/c/0bdd6121c8dd5f1764efe701ce26bb8e15acb172"},{"url":"https://git.kernel.org/stable/c/ad4ebae5dbc2d47b544aa54f03c12490065be08a"},{"url":"https://git.kernel.org/stable/c/048029ba1c793f8cabc4ad5eea765da01903f8f1"}],"title":"bpf: Require MEM_PERCPU for percpu kptr stores","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-98039","datePublished":"2026-09-25T10:23:52.360Z","dateReserved":"2026-09-25T10:19:56.071Z","dateUpdated":"2026-09-25T10:23:52.360Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-25 11:17:32","lastModifiedDate":"2026-09-25 11:17:32","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"98039","Ordinal":"1","Title":"bpf: Require MEM_PERCPU for percpu kptr stores","CVE":"CVE-2026-98039","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"98039","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Require MEM_PERCPU for percpu kptr stores\n\nmap_kptr_match_type() treats perm_flags as the set of register type flags\nthat a kptr field permits. Adding MEM_PERCPU to that set for\nBPF_KPTR_PERCPU does not require the source register to carry it, however.\nThe subset test consequently accepts both a plain bpf_obj_new() allocation\nand a referenced kernel pointer into a __percpu_kptr map field.\n\nLoads from the field are always marked MEM_PERCPU. Consumers then treat the\nstored value as the cookie returned by bpf_percpu_obj_new(): per-CPU pointer\nhelpers relocate it, and map teardown selects the per-CPU free path. A plain\nallocation can therefore provide an arbitrary kernel read/write, while a\nkernel pointer can be relocated into an invalid address or sent through a\nmissing destructor.\n\nRequire the source MEM_PERCPU flag to match the destination field kind.\nThis preserves valid bpf_percpu_obj_new() stores and rejects both the\nprogram-BTF and kernel-BTF variants.","Type":"Description","Title":"bpf: Require MEM_PERCPU for percpu kptr stores"}]}}}