Skip to content
Noroxi
NVD / CVE Program· CNA intel

CVE-2022-0001: Non-transparent sharing of branch predictor selectors between contexts in some Intel(R) Processors may allow an authorized user to potential

Noroxi assessment

Priority: Monitor (action score 26/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.50% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: linux (Debian:11) 5.10.103-1; linux (Debian:12) 5.16.12-1; linux (Debian:9) 4.9.303-1.
  • Mentioned 5 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to linux (Debian:11) 5.10.103-1; linux (Debian:12) 5.16.12-1; linux (Debian:9) 4.9.303-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Non-transparent sharing of branch predictor selectors between contexts in some Intel(R) Processors may allow an authorized user to potentially enable information disclosure via local access.

MediumCVSS 6.5 · v3.1—Proof of concept Fix available
Published
Mar 11, 2022
Updated
Jun 17, 2026
EPSS
0.5% · 43th percentile
CWE
—

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-0001

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
intelatom p5921b
intelatom p5931b
intelatom p5942b
intelatom p5962b
intelatom x6200fe
intelatom x6211e
intelatom x6212re
intelatom x6413e
intelatom x6425e
intelatom x6425re
intelatom x6427fe
intelceleron 5305u

and 188 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • intel atom p5921ball versions
  • intel atom p5931ball versions
  • intel atom p5942ball versions
  • intel atom p5962ball versions
  • intel atom x6200feall versions
  • intel atom x6211eall versions
  • intel atom x6212reall versions
  • intel atom x6413eall versions
  • intel atom x6425eall versions
  • intel atom x6425reall versions
  • intel atom x6427feall versions
  • intel celeron 5305uall versions
  • intel celeron 6305all versions
  • intel celeron 6305eall versions
  • intel celeron 6600heall versions
  • intel celeron g5205uall versions
  • intel celeron g5305uall versions
  • intel celeron g5900all versions
  • intel celeron g5900tall versions
  • intel celeron g5905all versions

Versions reported by the vendor

Affected version ranges reported by the assigning authority (intel). Independent of NVD's CPE analysis and usually ahead of it.

  • n/a Intel(R) Processors

    • See referencesaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11linuxbefore 5.10.103-15.10.103-1
Debian:12linuxbefore 5.16.12-15.16.12-1
Debian:9linuxbefore 4.9.303-14.9.303-1
openSUSE:Leap 15.3dtb-aarch64before 5.3.18-150300.59.54.15.3.18-150300.59.54.1
openSUSE:Leap 15.3kernel-64kbbefore 5.3.18-150300.59.54.15.3.18-150300.59.54.1
openSUSE:Leap 15.3kernel-azurebefore 5.3.18-150300.38.47.15.3.18-150300.38.47.1
openSUSE:Leap 15.3kernel-debugbefore 4.12.14-197.108.14.12.14-197.108.1
openSUSE:Leap 15.3kernel-debugbefore 5.3.18-150300.59.54.15.3.18-150300.59.54.1
openSUSE:Leap 15.3kernel-defaultbefore 4.12.14-197.108.14.12.14-197.108.1
openSUSE:Leap 15.3kernel-defaultbefore 5.3.18-150300.59.54.15.3.18-150300.59.54.1
openSUSE:Leap 15.3kernel-default-basebefore 5.3.18-150300.59.54.1.150300.18.35.35.3.18-150300.59.54.1.150300.18.35.3
openSUSE:Leap 15.3kernel-docsbefore 5.3.18-150300.59.54.15.3.18-150300.59.54.1
openSUSE:Leap 15.3kernel-kvmsmallbefore 5.3.18-150300.59.54.15.3.18-150300.59.54.1
openSUSE:Leap 15.3kernel-kvmsmallbefore 4.12.14-197.108.14.12.14-197.108.1
openSUSE:Leap 15.3kernel-obs-buildbefore 5.3.18-150300.59.54.15.3.18-150300.59.54.1
openSUSE:Leap 15.3kernel-obs-qabefore 5.3.18-150300.59.54.15.3.18-150300.59.54.1
openSUSE:Leap 15.3kernel-preemptbefore 5.3.18-150300.59.54.15.3.18-150300.59.54.1
openSUSE:Leap 15.3kernel-sourcebefore 5.3.18-150300.59.54.15.3.18-150300.59.54.1
openSUSE:Leap 15.3kernel-source-azurebefore 5.3.18-150300.38.47.15.3.18-150300.38.47.1
openSUSE:Leap 15.3kernel-symsbefore 5.3.18-150300.59.54.15.3.18-150300.59.54.1
openSUSE:Leap 15.3kernel-syms-azurebefore 5.3.18-150300.38.47.15.3.18-150300.38.47.1
openSUSE:Leap 15.3kernel-vanillabefore 4.12.14-197.108.14.12.14-197.108.1
openSUSE:Leap 15.3kernel-zfcpdumpbefore 5.3.18-150300.59.54.15.3.18-150300.59.54.1
openSUSE:Leap 15.3kernel-zfcpdumpbefore 4.12.14-197.108.14.12.14-197.108.1

+93

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:linux5.16.12-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch645.3.18-150300.59.54.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:kernel-64kb5.3.18-150300.59.54.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:kernel-azure5.3.18-150300.38.47.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:kernel-debug5.3.18-150300.59.54.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:kernel-default5.3.18-150300.59.54.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:kernel-default-base5.3.18-150300.59.54.1.150300.18.35.3 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:kernel-docs5.3.18-150300.59.54.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:kernel-kvmsmall5.3.18-150300.59.54.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:kernel-obs-build5.3.18-150300.59.54.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:kernel-obs-qa5.3.18-150300.59.54.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:kernel-source-azure5.3.18-150300.38.47.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:kernel-syms-azure5.3.18-150300.38.47.1 · openSUSE:Leap 15.3Package registry (OSV)
suse:kernel-azure5.3.18-150300.38.47.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP3Package registry (OSV)
suse:kernel-default4.4.121-92.169.1 · SUSE:Linux Enterprise Server 12 SP2-BCLPackage registry (OSV)
suse:kernel-default-base5.3.18-24.107.1.9.50.2 · SUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOSPackage registry (OSV)
suse:kernel-docs5.3.18-24.107.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP2_Update_251-5.5.1 · SUSE:Linux Enterprise Live Patching 15 SP2Package registry (OSV)
suse:kernel-obs-build5.3.18-24.107.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOSPackage registry (OSV)
suse:kernel-preempt5.3.18-24.107.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOSPackage registry (OSV)
suse:kernel-source4.4.121-92.169.1 · SUSE:Linux Enterprise Server 12 SP2-BCLPackage registry (OSV)
suse:kernel-source-azure5.3.18-150300.38.47.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP3Package registry (OSV)
suse:kernel-syms4.4.121-92.169.1 · SUSE:Linux Enterprise Server 12 SP2-BCLPackage registry (OSV)
suse:kernel-syms-azure5.3.18-150300.38.47.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP3Package registry (OSV)
suse:kgraft-patch-SLE12-SP4_Update_251-6.5.1 · SUSE:Linux Enterprise Live Patching 12 SP4Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02025-10-22

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+1320 d
  3. TodayOct 27, 2026+1691 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records