The Linux kernel BPF map function map_direct_value_addr incorrectly applies an offset to a computed address. A later call to resolve_pseudo_ldimm64 adds the same offset again, resulting in an address that is twice the intended value. This miscalculation can direct a BPF program to unintended memory locations, potentially enabling memory corruption or leakage. The CVE description does not identify a proven exploitation path, but the nature of the bug suggests that malicious BPF code could manipulate memory boundaries.

All Linux kernel releases that contain the buggy map_direct_value_addr implementation of BPF map handling are potentially impacted. The specific affected versions are not enumerated by the CNA; any kernel build that includes the referenced code before the associated bug‑fix commit would be susceptible.

No CVSS score is available, the EPSS score is not available, and the vulnerability is not listed in CISA's KEV catalog. Because the issue is tied to kernel internal address resolution, an attacker would need to craft a malicious BPF program to trigger the fault. In the absence of publicly documented exploitation, the risk remains indeterminate, but the potential for memory integrity compromise warrants preemptive mitigation.