{"id":"CVE-2026-90312","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Check load-acquire src ptr type before the load\n\ncheck_atomic_load() calls check_load_mem() before atomic_ptr_type_ok().\nFor a load-acquire that fetches into its o…","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Check load-acquire src ptr type before the load\n\ncheck_atomic_load() calls check_load_mem() before atomic_ptr_type_ok().\nFor a load-acquire that fetches into its o…","severity":"high","cvss":7.8,"cvssVector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","vendor":"Linux","product":"Linux","affected":["Linux >= c03bb2fa327e4c25d6c5360a8803a4b1cdc2d0b9 < 6ee7b00888498cf387dd30729e18a05328b94709","Linux >= c03bb2fa327e4c25d6c5360a8803a4b1cdc2d0b9 < 422a416041172af1ac610736d5f556d22b31b115","Linux >= c03bb2fa327e4c25d6c5360a8803a4b1cdc2d0b9 < b87803391baa7e0bef60549d8841f12e549ad057","Linux 6.15"],"published":"2026-09-17","updated":"2026-09-18","sourceUpdated":"2026-09-18T18:17:53.130","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-90312","references":[{"url":"https://git.kernel.org/stable/c/422a416041172af1ac610736d5f556d22b31b115","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/6ee7b00888498cf387dd30729e18a05328b94709","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"},{"url":"https://git.kernel.org/stable/c/b87803391baa7e0bef60549d8841f12e549ad057","label":"416baaa9-dc9f-4396-8d5f-8c081fb06d67"}],"tags":["nvd","cve.org"],"epss":0.00161,"epssPercentile":0.05766,"ingestedAt":"2026-09-17T16:21:47.826Z","slug":"CVE-2026-90312","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Check load-acquire src ptr type before the load\n\ncheck_atomic_load() calls check_load_mem() before atomic_ptr_type_ok().\nFor a load-acquire that fetches into its own source register (dst_reg ==\nsrc_reg), check_load_mem() overwrites src_reg's type with the type of the\nloaded value, so the subsequent atomic_ptr_type_ok() no longer sees the\nsource pointer and fails to reject the disallowed types (ctx, pkt,\nflow_keys, sock).\n\nSince bpf_convert_ctx_accesses() does not rewrite atomic loads, the raw\naccess to the underlying kernel object is left in place. The destination\ntype is taken from the ctx access itself, so a load-acquire of the sk\nfield of struct __sk_buff for example leaves the register typed as\nPTR_TO_SOCK_COMMON_OR_NULL, which type_is_sk_pointer() does not match\neither, while it actually holds unconverted struct sk_buff bytes. Once\nthe NULL check has passed this is a type confusion, not just a leak of\nkernel data.\n\nValidate src_reg with check_reg_arg() and check the source pointer type\nwith atomic_ptr_type_ok() before the load again, mirroring\ncheck_atomic_rmw(). Out-of-range register numbers are already rejected\nearlier by check_and_resolve_insns() (commit 503d21ef8eac (\"bpf: Do\nregister range validation early\")), and the only exemption there,\nis_stack_arg_ldx(), requires BPF_LDX | BPF_MEM | BPF_DW and thus never\nmatches a BPF_ATOMIC insn. atomic_ptr_type_ok() can therefore not\ndereference register state out of bounds, that is, the out-of-bounds\nread addressed by the Fixes commit below does not reappear (as proven\nalso via selftest).\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"twilight","depthScore":43,"depthScoreParts":{"impact":42.9,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[{"seq":207245,"id":"CVE-2026-90312","ts":1789757339867,"field":"cvss","old":null,"new":"7.8"},{"seq":207244,"id":"CVE-2026-90312","ts":1789757339867,"field":"severity","old":"none","new":"high"}]}