Exploited Known exploited (KEV) CVE-2022-0995

A four-year-old Linux kernel flaw enters KEV in 2026 — the catalog is not a list of new vulnerabilities

Linux Kernel Added to KEV Aug 26, 2026 Federal remediation due 2026-09-09

An out-of-bounds write in the Linux kernel was added to the CISA Known Exploited Vulnerabilities catalog on 2026-08-26. As its CVE number shows, it was assigned in 2022. It could allow a local user to gain privileged access or cause denial of service, with a due date 14 days out.

Key facts

  • CVE IDCVE-2022-0995
  • Affected (vendor / product)Linux Kernel
  • CWECWE-787
  • ExploitationListed in CISA KEV (exploitation confirmed)
  • Remediation due2026-09-09 (U.S. federal civilian agencies, BOD 22-01)

Key points

  • An out-of-bounds write (CWE-787) in the Linux kernel was added to KEV on 2026-08-26; the CVE number was assigned in 2022.
  • It could allow a local user to gain privileged access or cause denial of service — the type used to raise privileges after entry.
  • The condition for KEV listing is confirmed exploitation, not novelty.
  • CVE assignment years across the records this site holds as of 2026-09-02 run from 2002 to 2026, peaking at 2021 with 215.
  • KEV addition years at that date peak at 2022 with 555, reading as the catalog start-up period registering known cases together.

1Listing turns on exploitation, not novelty

The CISA Known Exploited Vulnerabilities catalog is often treated as a list of the most dangerous vulnerabilities right now. But the condition for listing is not novelty; it is confirmation that exploitation has actually occurred. This entry makes that plain. The CVE number was assigned in 2022 and the catalog addition is dated 2026-08-26 — roughly four years apart.

2The year assigned against the year listed

ItemDetail
CVE assignment year for this entry2022
KEV addition for this entry2026-08-26 (due 2026-09-09, a 14-day grace period)
Range of CVE assignment years across the records this site holds as of 2026-09-022002 through 2026
Most common assignment year at that date2021 with 215 (then 2025 with 185, 2023 with 165, 2024 with 164)
Distribution of KEV addition years at that date2021: 311, 2022: 555, 2023: 187, 2024: 186, 2025: 245, 2026: 203

The assignment years peak in 2021 with long tails on either side, reaching back to entries assigned in 2002 — vulnerabilities more than two decades old that were listed once exploitation was confirmed. On the addition side, 2022 stands out at 555, which reads as the catalog start-up period when known exploitation cases were registered together.

3Where privilege escalation sits

This entry concerns a local user gaining privileged access or causing denial of service. It is not a route for breaking in from outside but the type used to raise privileges by someone already inside. The reason it does not work to seal only the first stage of an intrusion is that second-stage tools like this persist for years.

Kernel vulnerabilities reach broadly, and Kernel appears among the leading product names in the records this site holds, with 31.

4A 14-day grace period

The due date is 14 days after the addition. Across the 1,687 records this site holds as of 2026-09-02, grace periods have a median of 21 days, a minimum of 1 and a maximum of 184, so this is somewhat on the short side. The required action is to apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use. Verify applicability with official vendor information and your own environment.

Why it matters

Running KEV as a list of recent vulnerabilities drops entries with older assignments. The operational lesson is to track the catalog by date added and not to set priority by assignment year.

FAQ

Why is an old CVE listed now?
Because listing turns on confirmed exploitation rather than novelty. If confirmation arrives later, an older assignment is still added.
If it is only exploitable locally, is the impact small?
It is the type used by someone already inside to raise privileges. That is why sealing only the first stage of an intrusion does not suffice.

Sources (primary)

This article is an independent organization based on the U.S. official data below. Always verify the exact, latest details and applicability with the official and vendor sources.

#Vulnerabilities#KEV#Linux#Privilege escalation#Kernel
Disclaimer: This site independently summarizes and classifies information based on official data sources. Always verify the latest and accurate information with the official sources. Content on finance, health, legal, and security is information, not advice. This site is not an official website of the U.S. government.