Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2019-11135: TSX Asynchronous Abort condition on some CPUs utilizing speculative execution may allow an authenticated user

45
This month
MEDIUM 6.5MITIGATEMITIGATEDOWNGRADE

CVE-2019-11135 is a medium-severity flaw (CVSS 6.5) affecting leap, fedora, slackware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

TSX Asynchronous Abort condition on some CPUs utilizing speculative execution may allow an authenticated user to potentially enable information disclosure via a side channel with local access.

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score6.5 (Medium)
Attack vectorLocal
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance3.1% (top 12%)
CISA exploited listNo
Published2019-11-14
Last modified2026-06-17
Publisher (CNA): Intel Corporation · Vendor: fedoraproject · hp · opensuse · slackware

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

opensuse leap MITIGATE
Affected: 15.0 · 15.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 15.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
fedoraproject fedora MITIGATE
Affected: 30 · 31
Fixed in: no fixed release known
Safe to downgrade to: a release before 30
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
slackware slackware DOWNGRADE
Affected: 14.2
Fixed in: no fixed release known
Safe to downgrade to: a release before 14.2
1. Check installed version
apt-cache policy slackware || rpm -q slackware || slackware --version
2. No fixed release: DOWNGRADE to a release before 14.2 (Debian / Ubuntu)
apt-cache madison slackware sudo apt install slackware=<VERSION_BEFORE_14.2> sudo apt-mark hold slackware
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list slackware sudo dnf downgrade slackware-<VERSION_BEFORE_14.2> sudo dnf versionlock add slackware
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
hp apollo 4200 firmware UPGRADE
Affected: < 2.20
Fixed in: 2.20
Safe to downgrade to: no unaffected older release
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
hp apollo 2000 firmware UPGRADE
Affected: < 2.20
Fixed in: 2.20
Safe to downgrade to: no unaffected older release
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
hp proliant bl460c firmware UPGRADE
Affected: < 2.20
Fixed in: 2.20
Safe to downgrade to: no unaffected older release
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-11135?

leap: mitigate or apply the listed mitigation; fedora: mitigate or apply the listed mitigation; slackware: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-11135 being exploited?

CVE-2019-11135 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-11135 affect?

CVE-2019-11135 affects leap, fedora, slackware. Severity is medium (CVSS 6.5). TSX Asynchronous Abort condition on some CPUs utilizing speculative execution may allow an authenticated user to potentially enable information disclosure via a side channel with local access.

How urgent is CVE-2019-11135?

Priority 45/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.