Skip to content

CVE-2022-2586

It was discovered that a nft object or expression could reference a nft set on a different nft table, leading to a use-after-free once that table was deleted.

CVSS
5.3Mediumscored by the publisher (CNA)
Exploited in the wild
Yes, in CISA KEV since 26 Jun 2024CISA deadline for US federal agencies: 17 Jul 2024unvetted proof-of-concept code on github
EPSS
10.2%chance of exploitation in the next 30 daystop 5% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
8 Jan 2024analysed here 12 Nov 2026

Do first. Apply updates per vendor instructions or discontinue use of the product if updates are unavailable. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
local
Weakness

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
The Linux Kernel Organization linux>= 3.16 and < 4.14.316>= 4.15 and < 4.19.256>= 4.20 and < 5.4.211>= 5.5 and < 5.10.137>= 5.11 and < 5.15.61>= 5.16 and < 5.18.18>= 5.19 and < 5.19.2Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • siemens:simatic_s7-1500_tm_mfp_firmware
  • siemens:sinec_os
  • linux:linux_kernel
  • canonical:ubuntu_linux

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 26 Jun 2024.
CISA due date
17 Jul 2024, the remediation deadline for US federal agencies
CISA required action
Apply updates per vendor instructions or discontinue use of the product if updates are unavailable.
Public exploit code
Unvetted proof-of-concept code on GitHub: 3 GitHub proofs of concept
CISA SSVC
exploitation active, automatable no, technical impact totalAssessed by CISA 26 Jun 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 3 Sept 2022First proof-of-concept repository on GitHub (unvetted)
  2. 8 Jan 2024Published493 days (about 1 year) later
  3. 26 Jun 2024Added to CISA KEV (exploited in the wild)169 days (about 6 months) later
  4. 26 Jun 2024CISA SSVC assessment: exploitation active1 day later
  5. 17 Jul 2024CISA remediation due date (US federal agencies)20 days later
  6. 14 Oct 2026CVE record last updated820 days (about 2 years) later
  7. 12 Nov 2026Analysed by vulneraibility.com29 days later

CVSS vector

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

MetricValueWhat it means
Attack vectorLocalLocal access required (shell, logged-in user).
Attack complexityHighNeeds specific conditions, a race or a particular configuration.
Privileges requiredLowThe attacker needs basic user privileges.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityNoneNo data disclosure.
IntegrityLowLimited modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2022-2586 being exploited?

Yes. CVE-2022-2586 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2022-2586?

CVE-2022-2586 is rated Medium with a CVSS score of 5.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2022-2586?

Yes. A fix has been recorded for CVE-2022-2586. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2022-2586 affect?

CVE-2022-2586 affects siemens:simatic_s7-1500_tm_mfp_firmware, siemens:sinec_os, linux:linux_kernel, canonical:ubuntu_linux. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

17 references in the CVE record, grouped by the tags the record gives them.

Advisories (9)

Show 3 more

Other links (8)

Show 2 more

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com