In the Linux kernel, the BPF verifier incorrectly copies the identifier of a register when synchronizing linked registers. When a register is modified by adding an offset, the verifier assigns a new constant identifier but fails to preserve the original link. Subsequent verification steps that depend on the original bounds are therefore misapplied, allowing a program that divides by zero or otherwise violates safety checks to be accepted. The flaw is a logic error in the BPF verifier's register‑id handling, leading to a denial‑of‑service due to incorrect bounds propagation. The impact concerns the integrity and availability of the system when executing BPF bytecode provided by user space.

The vulnerability affects all Linux kernel releases that include the flawed BPF verifier code, with no specific version boundary provided. Systems running the standard Linux kernel in any configuration that enables BPF program loading are potentially affected. The CVE entry lists the Linux kernel as the affected product. No vendor‑specific patches or version qualifiers are supplied in the data.

The CVSS score is not supplied, and the EPSS score is unavailable, so the exact quantitative risk cannot be determined from the data. The flaw is not marked in the CISA KEV catalog. Attackers who can inject arbitrary BPF programs—such as users with the ability to load programs via `ioctl` or `perf_event_open`—may exploit the flawed verifier to craft bytecode that will be considered safe while violating operations like division by zero. The required conditions are an ability to load a custom BPF program, which is possible for any user with the appropriate kernel capabilities or for applications that embed BPF, such as networking stacks, container runtimes, or performance tracing utilities. The likely attack vector is local or at the privileged level, depending on the capabilities of the attacker. From the information given, it is inferred that this bug can allow a denial of service or to relax verifier checks, thereby enabling unintended code paths. No specific exploitation evidence is cited, but the nature of the flaw indicates a high potential for impact if an attacker can supply crafted programs.