# CVE-2020-10767: Security feature bypass in kernel

> A local attacker can bypass Spectre V2 mitigations in the Linux kernel when specific CPU features are unavailable, leading to potential information disclosure.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** A-156766097, ASB-A-156766097, DEBIAN-CVE-2020-10767, GHSA-hmrm-3xmg-v873, UBUNTU-CVE-2020-10767

## What is CVE-2020-10767?

CVE-2020-10767 is a medium-severity vulnerability in Linux kernel, published on 15 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in the Linux kernel before 5.8-rc1 in the implementation of the Enhanced IBPB (Indirect Branch Prediction Barrier). The IBPB mitigation will be disabled when STIBP is not available or when the Enhanced Indirect Branch Restricted Speculation (IBRS) is available. This flaw allows a local attacker to perform a Spectre V2 style attack when this configuration is active. The highest threat from this vulnerability is to confidentiality.

Weakness: CWE-440 (Expected Behavior Violation)

## Which versions are affected by CVE-2020-10767?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2020-10767?

Upgrade to a fixed version.

## Is CVE-2020-10767 being exploited?

There is no known exploitation of CVE-2020-10767 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10767 and fix it if it is affected.

What it is: CVE-2020-10767 is a medium-severity vulnerability in Linux kernel, published on 15 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10767 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-10767/ (Markdown: https://insights.sbomify.com/CVE-2020-10767/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-10767
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-10767
- OSV: https://osv.dev/vulnerability/CVE-2020-10767

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-10767/
Summaries are generated and may contain mistakes; the official description above is the record.