OESA-2022-2144 (CVE-2022-3643)
Vulnerability from osv_openeuler – Published: 2022-12-24 11:05 – Updated: 2026-08-06 11:05 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
Guests can trigger NIC interface reset/abort/crash via netback It is possible for a guest to trigger a NIC interface reset/abort/crash in a Linux based network backend by sending certain kinds of packets. It appears to be an (unwritten?) assumption in the rest of the Linux network stack that packet protocol headers are all contained within the linear section of the SKB and some NICs behave badly if this is not the case. This has been reported to occur with Cisco (enic) and Broadcom NetXtrem II BCM5780 (bnx2x) though it may be an issue with other NICs/drivers as well. In case the frontend is sending requests with split headers, netback will forward those violating above mentioned assumption to the networking core, resulting in said misbehavior.(CVE-2022-3643)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"kernel-debuginfo-4.19.90-2212.3.0.0182.oe1.aarch64.rpm",
"bpftool-debuginfo-4.19.90-2212.3.0.0182.oe1.aarch64.rpm",
"perf-debuginfo-4.19.90-2212.3.0.0182.oe1.aarch64.rpm",
"kernel-source-4.19.90-2212.3.0.0182.oe1.aarch64.rpm",
"kernel-debugsource-4.19.90-2212.3.0.0182.oe1.aarch64.rpm",
"bpftool-4.19.90-2212.3.0.0182.oe1.aarch64.rpm",
"python3-perf-4.19.90-2212.3.0.0182.oe1.aarch64.rpm",
"python2-perf-debuginfo-4.19.90-2212.3.0.0182.oe1.aarch64.rpm",
"perf-4.19.90-2212.3.0.0182.oe1.aarch64.rpm",
"kernel-devel-4.19.90-2212.3.0.0182.oe1.aarch64.rpm",
"kernel-tools-4.19.90-2212.3.0.0182.oe1.aarch64.rpm",
"python2-perf-4.19.90-2212.3.0.0182.oe1.aarch64.rpm",
"python3-perf-debuginfo-4.19.90-2212.3.0.0182.oe1.aarch64.rpm",
"kernel-tools-debuginfo-4.19.90-2212.3.0.0182.oe1.aarch64.rpm",
"kernel-tools-devel-4.19.90-2212.3.0.0182.oe1.aarch64.rpm",
"kernel-4.19.90-2212.3.0.0182.oe1.aarch64.rpm"
],
"src": [
"kernel-4.19.90-2212.3.0.0182.oe1.src.rpm"
],
"x86_64": [
"kernel-debuginfo-4.19.90-2212.3.0.0182.oe1.x86_64.rpm",
"kernel-tools-4.19.90-2212.3.0.0182.oe1.x86_64.rpm",
"kernel-4.19.90-2212.3.0.0182.oe1.x86_64.rpm",
"bpftool-debuginfo-4.19.90-2212.3.0.0182.oe1.x86_64.rpm",
"python2-perf-debuginfo-4.19.90-2212.3.0.0182.oe1.x86_64.rpm",
"perf-4.19.90-2212.3.0.0182.oe1.x86_64.rpm",
"kernel-debugsource-4.19.90-2212.3.0.0182.oe1.x86_64.rpm",
"bpftool-4.19.90-2212.3.0.0182.oe1.x86_64.rpm",
"python3-perf-4.19.90-2212.3.0.0182.oe1.x86_64.rpm",
"kernel-devel-4.19.90-2212.3.0.0182.oe1.x86_64.rpm",
"perf-debuginfo-4.19.90-2212.3.0.0182.oe1.x86_64.rpm",
"python2-perf-4.19.90-2212.3.0.0182.oe1.x86_64.rpm",
"python3-perf-debuginfo-4.19.90-2212.3.0.0182.oe1.x86_64.rpm",
"kernel-tools-debuginfo-4.19.90-2212.3.0.0182.oe1.x86_64.rpm",
"kernel-tools-devel-4.19.90-2212.3.0.0182.oe1.x86_64.rpm",
"kernel-source-4.19.90-2212.3.0.0182.oe1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP3",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-20.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.19.90-2212.3.0.0182.oe1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Critical"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nGuests can trigger NIC interface reset/abort/crash via netback It is possible for a guest to trigger a NIC interface reset/abort/crash in a Linux based network backend by sending certain kinds of packets. It appears to be an (unwritten?) assumption in the rest of the Linux network stack that packet protocol headers are all contained within the linear section of the SKB and some NICs behave badly if this is not the case. This has been reported to occur with Cisco (enic) and Broadcom NetXtrem II BCM5780 (bnx2x) though it may be an issue with other NICs/drivers as well. In case the frontend is sending requests with split headers, netback will forward those violating above mentioned assumption to the networking core, resulting in said misbehavior.(CVE-2022-3643)",
"id": "OESA-2022-2144",
"modified": "2026-08-06T11:05:27Z",
"published": "2022-12-24T11:05:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2022-2144"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-3643"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2022-3643"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.