CVE-2022-1966
Public on
Last Modified:
Description
[REJECTED CVE] A use-after-free vulnerability has been identified in the Linux Kernel's netfilter subsystem that did not properly handle the removal of stateful expressions in some situations. A local attacker could use this to cause a denial of service (system crash) or execute arbitrary code.
Statement
This CVE has been rejected. This candidate is a duplicate of CVE-2022-32250. Note: All CVE users should reference CVE-2022-32250 instead of this candidate.
Additional Information
- This content is not included.Bugzilla 2093146: kernel: netfilter: nf_tables: incorrect NFT_STATEFUL_EXPR check leads to a use-after-free (write)
- Content from cwe.mitre.org is not included.CWE-416: Use After Free
- FAQ: Frequently asked questions about CVE-2022-1966
- Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.
External References
Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2022-1966
Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2022-1966
Affected Packages and Issued Red Hat Security Errata
| Products / Services | Components | State | Errata |
|---|---|---|---|
| Red Hat Enterprise Linux 6 | kernel | Under investigation | |
| Red Hat Enterprise Linux 7 | kpatch-patch | Fixed | RHSA-2022:5216 |
| Red Hat Enterprise Linux 7 | kernel | Fixed | RHSA-2022:5232 |
| Red Hat Enterprise Linux 7 | kernel-rt | Fixed | RHSA-2022:5236 |
| Red Hat Enterprise Linux 8 | kernel | Under investigation | |
| Red Hat Enterprise Linux 8 | kernel-rt | Under investigation | |
| Red Hat Enterprise Linux 8.2 Extended Update Support | kernel | Fixed | RHSA-2022:5220 |
| Red Hat Enterprise Linux 8.2 Extended Update Support | kernel-rt | Fixed | RHSA-2022:5224 |
| Red Hat Enterprise Linux 8.2 Extended Update Support | kpatch-patch | Fixed | RHSA-2022:5476 |
| Red Hat Enterprise Linux 9 | kpatch-patch | Fixed | RHSA-2022:5214 |
| Red Hat Enterprise Linux 9 | kernel | Fixed | RHSA-2022:5249 |
| Red Hat Enterprise Linux 9 | kernel-rt | Fixed | RHSA-2022:5267 |
| Red Hat Virtualization 4 for Red Hat Enterprise Linux 7 | redhat-virtualization-host | Fixed | RHSA-2022:5439 |
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
For more information, see https://access.redhat.com/solutions/762393.
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
- "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
- "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.
What can I do if my product is listed as "Will not fix"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
What can I do if my product is listed as "Fix deferred"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
- Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
Not sure what something means? Check out our Security Glossary.