CVE-2022-42722 — In the Linux kernel 5.8 through 5.19.14, local attackers able to inject WLAN frames into the...
In the Linux kernel 5.8 through 5.19.x before 5.19.16, local attackers able to inject WLAN frames into the mac80211 stack could cause a NULL pointer dereference denial-of-service attack against the beacon protection of P2P devices.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.6% (30-day exploitation probability)+7
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — bugzilla.suse.com (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Fedoraproject Fedora, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Debian | Debian Linux | version 10.0version 11.0 | Vulnerable | NIST National Vulnerability Database |
| Fedoraproject | Fedora | version 35version 36version 37 | Vulnerable | NIST National Vulnerability Database |
| Linux | Linux Kernel | ≥ 5.8 and < 5.19.16 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Fix documented
- Affected products added · linux/linux kernel, fedoraproject/fedora, debian/debian linux
- CVSS changed · 5.5
- Source status changed · → Modified
- Record created in this database
- 2022
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
16 on the record
- bugzilla.suse.com/show_bug.cgi
- git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless.git/commit/
- security.netapp.com/advisory/ntap-20230203-0008/
- packetstormsecurity.com/files/169951/Kernel-Live-Patch-Security-Notice-LSN-0090-1.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/S2KT
- www.openwall.com/lists/oss-security/2022/10/13/5
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S2KTU5
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VNN3
- www.debian.org/security/2022/dsa-5257
- lists.debian.org/debian-lts-announce/2022/11/msg00001.html
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VNN3VF
- nvd.nist.gov/vuln/detail/CVE-2022-42722
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/GGHE
- github.com/advisories/GHSA-wfvm-966j-jch4
- cert-portal.siemens.com/productcert/html/ssa-794697.html
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GGHENN
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-98164 KVM: x86/mmu: Check write tracking in all address spaces 16d
- High CVE-2026-98163 cgroup: Avoid iteration of dying tasks with zero refcount 19d
- Medium CVE-2026-98162 smb/server: fix tree connection leak in smb2_tree_connect() 20d
- High CVE-2026-98156 drm/virtio: use the DMA API for resource backing on Xen 20d
- Medium CVE-2026-98159 wifi: mt76: mt7921: validate CLC firmware records 20d
- Medium CVE-2026-98138 ntfs: do not mark the volume clean in sync_fs when errors were recorded 20d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2022-42722 is "In the Linux kernel 5.8 through 5.19.14, local attackers able to inject WLAN frames into the...", rated Medium. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.60% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.