Symbolic Name not Mapping to Correct Object
CWE-386
A constant symbolic reference to an object is used, even though the reference can resolve to a different object over time.
We track 2 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 7.7.
Latest Symbolic Name not Mapping to Correct Object vulnerabilities
- 7.8 High severity
Linux: Symbolic Name not Mapping to Correct Object
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 (a
- 7.5 High severity
Firefox: Symbolic Name not Mapping to Correct Object
GetBoundName could return the wrong version of an object when JIT optimizations were applied. This vulnerability affects Firefox < 125, Firefox ESR < 115.10, and Thunderbird < 115.10.