Answer in brief
CVE-2026-53081 records a High severity (CVSS 7.8) vulnerability in bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-53081 records a High severity (CVSS 7.8) vulnerability in bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=98d7ca374ba4b39e7535613d40e159f09ca14da2 <13c02881e49aac4c82b261faa26db9edf2567231 || >=98d7ca374ba4b39e7535613d40e159f09ca14da2 <691adf738817275368ed56311b7d798d617823a3 || >=98d7ca374ba4b39e7535613d40e159f09ca14da2 <7d73c72cccac651acc891377a5e623e4021c6380 || >=98d7ca374ba4b39e7535613d40e159f09ca14da2 <2f2ec8e7730e21fc9bd49e0de9cdd58213ea24d0 | 13c02881e49aac4c82b261faa26db9edf2567231, 691adf738817275368ed56311b7d798d617823a3, 7d73c72cccac651acc891377a5e623e4021c6380, 2f2ec8e7730e21fc9bd49e0de9cdd58213ea24d0 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
In the Linux kernel, the following vulnerability has been resolved: bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars When regsafe() compares two scalar registers that both carry BPF_ADD_CONST, check_scalar_ids() maps their full compound id (aka base | BPF_ADD_CONST flag) as one idmap entry. However, it never verifies that the underlying base ids, that is, with the flag stripped are consistent with existing idmap mappings. This allows construction of two verifier states where the old state has R3 = R2 + 10 (both sharing base id A) while the current state has R3 = R4 + 10 (base id C, unrelated to R2). The idmap creates two independent entries: A->B (for R2) and A|flag->C|flag (for R3), without catching that A->C conflicts with A->B. State pruning then incorrectly succeeds. Fix this by additionally verifying base ID mapping consistency whenever BPF_ADD_CONST is set: after mapping the compound ids, also invoke check_ids() on the base IDs (flag bits stripped). This ensures that if A was already mapped to B from comparing the source register, any ADD_CONST derivative must also derive from B, not an unrelated C.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=98d7ca374ba4b39e7535613d40e159f09ca14da2 <13c02881e49aac4c82b261faa26db9edf2567231 || >=98d7ca374ba4b39e7535613d40e159f09ca14da2 <691adf738817275368ed56311b7d798d617823a3 || >=98d7ca374ba4b39e7535613d40e159f09ca14da2 <7d73c72cccac651acc891377a5e623e4021c6380 || >=98d7ca374ba4b39e7535613d40e159f09ca14da2 <2f2ec8e7730e21fc9bd49e0de9cdd58213ea24d0 | 13c02881e49aac4c82b261faa26db9edf2567231, 691adf738817275368ed56311b7d798d617823a3, 7d73c72cccac651acc891377a5e623e4021c6380, 2f2ec8e7730e21fc9bd49e0de9cdd58213ea24d0 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
In the Linux kernel, the following vulnerability has been resolved: bpf: Enforce regsafe base id consistency for BPF_ADD_CONST scalars When regsafe() compares two scalar registers that both carry BPF_ADD_CONST, check_scalar_ids() maps their full compound id (aka base | BPF_ADD_CONST flag) as one idmap entry. However, it never verifies that the underlying base ids, that is, with the flag stripped are consistent with existing idmap mappings. This allows construction of two verifier states where the old state has R3 = R2 + 10 (both sharing base id A) while the current state has R3 = R4 + 10 (base id C, unrelated to R2). The idmap creates two independent entries: A->B (for R2) and A|flag->C|flag (for R3), without catching that A->C conflicts with A->B. State pruning then incorrectly succeeds. Fix this by additionally verifying base ID mapping consistency whenever BPF_ADD_CONST is set: after mapping the compound ids, also invoke check_ids() on the base IDs (flag bits stripped). This ensures that if A was already mapped to B from comparing the source register, any ADD_CONST derivative must also derive from B, not an unrelated C.
Quoted source text, attributed separately from HOL analysis.