Linux: Symbolic Name not Mapping to Correct Object
CVE-2026-53081 is a high-severity symbolic name not mapping to correct object vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 13c02881e49aac4c82b261faa26db9edf2567231, 691adf738817275368ed56311b7d798d617823a3, 7d73c72cccac651acc891377a5e623e4021c6380 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.18% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 13c02881e49aac4c82b261faa26db9edf2567231 or 691adf738817275368ed56311b7d798d617823a3 or 7d73c72cccac651acc891377a5e623e4021c6380 or 2f2ec8e7730e21fc9bd49e0de9cdd58213ea24d0, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.12.91 or 6.18.33 or 7.0.10, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 98d7ca374ba4b39e7535613d40e159f09ca14da2 up to, but not including, 13c02881e49aac4c82b261faa26db9edf2567231; 98d7ca374ba4b39e7535613d40e159f09ca14da2 up to, but not including, 691adf738817275368ed56311b7d798d617823a3; 98d7ca374ba4b39e7535613d40e159f09ca14da2 up to, but not including, 7d73c72cccac651acc891377a5e623e4021c6380; 98d7ca374ba4b39e7535613d40e159f09ca14da2 up to, but not including, 2f2ec8e7730e21fc9bd49e0de9cdd58213ea24d0; 6.11 | 13c02881e49aac4c82b261faa26db9edf2567231, 691adf738817275368ed56311b7d798d617823a3, 7d73c72cccac651acc891377a5e623e4021c6380, 2f2ec8e7730e21fc9bd49e0de9cdd58213ea24d0 |
| Red Hat | Red Hat Enterprise Linux 10 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 6 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 9 | Not specified in the record | Not stated |
| Linux | Linux Kernel | 6.11 up to, but not including, 6.12.91; 6.13 up to, but not including, 6.18.33; 6.19 up to, but not including, 7.0.10 | 6.12.91, 6.18.33, 7.0.10 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA |
| CVSS 3.1 | 6.4 | Medium | CNA |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Symbolic Name not Mapping to Correct Object
A constant symbolic reference to an object is used, even though the reference can resolve to a different object over time.
More Symbolic Name not Mapping to Correct Object vulnerabilities (CWE-386)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Third-party and government advisories
- access.redhat.com/security/cve/CVE-2026-53081Third Party Advisory
- bugzilla.redhat.com/show_bug.cgi?id=2492322Third Party Advisory
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-53081.jsonThird Party Advisory
Recent Symbolic Name not Mapping to Correct Object vulnerabilities
- 7.5 High severity
Spotted an error? Tell us.