{"api_version":"1","generated_at":"2026-05-06T11:04:31+00:00","cve":"CVE-2026-31734","urls":{"html":"https://cve.report/CVE-2026-31734","api":"https://cve.report/api/cve/CVE-2026-31734.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-31734","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-31734"},"summary":{"title":"sched_ext: Fix is_bpf_migration_disabled() false negative on non-PREEMPT_RCU","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nsched_ext: Fix is_bpf_migration_disabled() false negative on non-PREEMPT_RCU\n\nSince commit 8e4f0b1ebcf2 (\"bpf: use rcu_read_lock_dont_migrate() for\ntrampoline.c\"), the BPF prolog (__bpf_prog_enter) calls migrate_disable()\nonly when CONFIG_PREEMPT_RCU is enabled, via rcu_read_lock_dont_migrate().\nWithout CONFIG_PREEMPT_RCU, the prolog never touches migration_disabled,\nso migration_disabled == 1 always means the task is truly\nmigration-disabled regardless of whether it is the current task.\n\nThe old unconditional p == current check was a false negative in this\ncase, potentially allowing a migration-disabled task to be dispatched to\na remote CPU and triggering scx_error in task_can_run_on_remote_rq().\n\nOnly apply the p == current disambiguation when CONFIG_PREEMPT_RCU is\nenabled, where the ambiguity with the BPF prolog still exists.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-05-01 15:16:36","updated_at":"2026-05-01 15:24:14"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/72c43eb2e334febe93018cfb68ae828f55c6e49e","name":"https://git.kernel.org/stable/c/72c43eb2e334febe93018cfb68ae828f55c6e49e","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/0c4a59df370bea245695c00aaae6ae75747139bd","name":"https://git.kernel.org/stable/c/0c4a59df370bea245695c00aaae6ae75747139bd","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b4992a9446bb9a639007bfd32bf5c5a7e30199e5","name":"https://git.kernel.org/stable/c/b4992a9446bb9a639007bfd32bf5c5a7e30199e5","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-31734","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31734","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 8e4f0b1ebcf2180ab594f204f01279a666dadf3b 72c43eb2e334febe93018cfb68ae828f55c6e49e git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 8e4f0b1ebcf2180ab594f204f01279a666dadf3b b4992a9446bb9a639007bfd32bf5c5a7e30199e5 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 8e4f0b1ebcf2180ab594f204f01279a666dadf3b 0c4a59df370bea245695c00aaae6ae75747139bd git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.18","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.22 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.19.12 6.19.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"31734","cve":"CVE-2026-31734","epss":"0.000170000","percentile":"0.040610000","score_date":"2026-05-05","updated_at":"2026-05-06 00:08:10"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["kernel/sched/ext_idle.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"72c43eb2e334febe93018cfb68ae828f55c6e49e","status":"affected","version":"8e4f0b1ebcf2180ab594f204f01279a666dadf3b","versionType":"git"},{"lessThan":"b4992a9446bb9a639007bfd32bf5c5a7e30199e5","status":"affected","version":"8e4f0b1ebcf2180ab594f204f01279a666dadf3b","versionType":"git"},{"lessThan":"0c4a59df370bea245695c00aaae6ae75747139bd","status":"affected","version":"8e4f0b1ebcf2180ab594f204f01279a666dadf3b","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["kernel/sched/ext_idle.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.18"},{"lessThan":"6.18","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.22","versionType":"semver"},{"lessThanOrEqual":"6.19.*","status":"unaffected","version":"6.19.12","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.0","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.22","versionStartIncluding":"6.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.19.12","versionStartIncluding":"6.18","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0","versionStartIncluding":"6.18","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nsched_ext: Fix is_bpf_migration_disabled() false negative on non-PREEMPT_RCU\n\nSince commit 8e4f0b1ebcf2 (\"bpf: use rcu_read_lock_dont_migrate() for\ntrampoline.c\"), the BPF prolog (__bpf_prog_enter) calls migrate_disable()\nonly when CONFIG_PREEMPT_RCU is enabled, via rcu_read_lock_dont_migrate().\nWithout CONFIG_PREEMPT_RCU, the prolog never touches migration_disabled,\nso migration_disabled == 1 always means the task is truly\nmigration-disabled regardless of whether it is the current task.\n\nThe old unconditional p == current check was a false negative in this\ncase, potentially allowing a migration-disabled task to be dispatched to\na remote CPU and triggering scx_error in task_can_run_on_remote_rq().\n\nOnly apply the p == current disambiguation when CONFIG_PREEMPT_RCU is\nenabled, where the ambiguity with the BPF prolog still exists."}],"providerMetadata":{"dateUpdated":"2026-05-01T14:14:32.217Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/72c43eb2e334febe93018cfb68ae828f55c6e49e"},{"url":"https://git.kernel.org/stable/c/b4992a9446bb9a639007bfd32bf5c5a7e30199e5"},{"url":"https://git.kernel.org/stable/c/0c4a59df370bea245695c00aaae6ae75747139bd"}],"title":"sched_ext: Fix is_bpf_migration_disabled() false negative on non-PREEMPT_RCU","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-31734","datePublished":"2026-05-01T14:14:32.217Z","dateReserved":"2026-03-09T15:48:24.137Z","dateUpdated":"2026-05-01T14:14:32.217Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-05-01 15:16:36","lastModifiedDate":"2026-05-01 15:24:14","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"31734","Ordinal":"1","Title":"sched_ext: Fix is_bpf_migration_disabled() false negative on non","CVE":"CVE-2026-31734","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"31734","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nsched_ext: Fix is_bpf_migration_disabled() false negative on non-PREEMPT_RCU\n\nSince commit 8e4f0b1ebcf2 (\"bpf: use rcu_read_lock_dont_migrate() for\ntrampoline.c\"), the BPF prolog (__bpf_prog_enter) calls migrate_disable()\nonly when CONFIG_PREEMPT_RCU is enabled, via rcu_read_lock_dont_migrate().\nWithout CONFIG_PREEMPT_RCU, the prolog never touches migration_disabled,\nso migration_disabled == 1 always means the task is truly\nmigration-disabled regardless of whether it is the current task.\n\nThe old unconditional p == current check was a false negative in this\ncase, potentially allowing a migration-disabled task to be dispatched to\na remote CPU and triggering scx_error in task_can_run_on_remote_rq().\n\nOnly apply the p == current disambiguation when CONFIG_PREEMPT_RCU is\nenabled, where the ambiguity with the BPF prolog still exists.","Type":"Description","Title":"sched_ext: Fix is_bpf_migration_disabled() false negative on non"}]}}}