What is CVE-2022-0995?A high-severity flaw criminals are using now.
CVE-2022-0995 is a high-severity flaw (CVSS 7.8) in Linux kernel, published on 25 March 2022. It is on the list of flaws known to be exploited, so criminals are already using it. The latest forecast puts its chance of use in the next 30 days at 8.9%. If you run an affected version, patch it first.
Published 25 March 2022. Record last updated 9 November 2023. We keep this page's data up to date.
What is CVE-2022-0995? In plain terms.
An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
An out-of-bounds (OOB) memory write flaw was found in the Linux kernel’s watch_queue event notification subsystem. This flaw can overwrite parts of the kernel state, potentially allowing a local user to gain privileged access or cause a denial of service on the system.
What kind of flaw is it?
- CWE-787Out-of-bounds Write
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAlready on the device
- How hard it is to pull offEasy: no special conditions
- Login needed firstAn ordinary user account
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data, change data and take it offline
Severity vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is CVE-2022-0995 being exploited? Yes.
Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 8.9%.
Timeline
- Published
- Record last updated
- Exploit likelihood jumped
- Exploit likelihood fell
- Added to the known-exploited list
CVE-2022-0995 scores 75. Action: Emergency patch.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2022-0995 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2022-0995? 24 products.
The published record lists 24 products from 3 vendors. Versions are shown as published: "5.8 to before 5.10.106" means from 5.8 up to, but not including, 5.10.106. If you run one of these, check your version, then go to the fix below.
- Operating system
Linux kernel
by Linux
Affected versions5.8 to before 5.10.1065.11 to before 5.15.295.16 to before 5.16.55.17-rc15.17-rc25.17-rc35.17-rc45.17-rc55.17-rc65.17-rc7 - Operating system
Fedora
Affected versions35 - Hardware
H300e
by Netapp
Affected versionsversion not specified - Operating system
H300e Firmware
by Netapp
Affected versionsversion not specified - Hardware
H300s
by Netapp
Affected versionsversion not specified - Operating system
H300s Firmware
by Netapp
Affected versionsversion not specified - Hardware
H410c
by Netapp
Affected versionsversion not specified - Operating system
H410c Firmware
by Netapp
Affected versionsversion not specified - Hardware
H410s
by Netapp
Affected versionsversion not specified
How do I fix CVE-2022-0995? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Check it wasn’t used before you patchedBecause criminals are already using this flaw, look for signs of a break-in on affected systems using the vendor’s guidance.
References
5 linksDoes CVE-2022-0995 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
An out-of-bounds (OOB) memory write flaw was found in the Linux kernel’s watch_queue event notification subsystem. This flaw can overwrite parts of the kerne...
- Matched to
- Linux kernel on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2022-0995 is a high-severity flaw in Linux kernel, published on 25 March 2022. An attacker has to be already on the device with an ordinary user account, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
It scores 7.8 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2022-0995 is 75 out of 100, which is High. Its action is "Emergency patch". Attackers are using this flaw today. If you run an affected version, it goes to the top of your list.
Attackers are already using it. It is on the government list of flaws known to be exploited, and the latest forecast puts the chance of it being used in the next 30 days at 8.9%.
For Linux kernel: 5.8 to before 5.10.106, 5.11 to before 5.15.29, 5.16 to before 5.16.5, 5.17-rc1, 5.17-rc2, 5.17-rc3 and 4 more. The record lists 24 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet. Because criminals are already using it, also check affected systems for signs of a break-in.