Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in kprobe/kretprobe tracing test code. A local, low-privileged actor could cause kernel memory to be consumed, potentially affecting availability. The sources do not show remote attackability, data theft, integrity impact, or active exploitation.
Executive priority
Treat as a normal kernel availability fix, not an emergency internet-facing incident. Prioritize patching shared Linux systems and hosts with untrusted local users, then fold remaining systems into routine kernel maintenance.
Technical view
The affected functions test_gen_kprobe_cmd() and test_gen_kretprobe_cmd() allocated a buffer and freed it only on failure. Successful paths leaked about 2048 bytes per observed object. The CVSS vector is local, low complexity, low privileges, no user interaction, and high availability impact.
Likely exposure
Exposure is most likely on systems running affected Linux kernel versions where local users can exercise the affected tracing kprobe/kretprobe test path. Internet-facing exposure is not indicated by the provided sources.
Exploitation context
No KEV listing is provided, and the source bundle does not cite active exploitation. The described impact is local denial of service through memory exhaustion rather than confidentiality or integrity compromise.
Researcher notes
Evidence is limited to the CVE record and kernel stable commit references. The affected list in the bundle is version-oriented but not a full distribution matrix, so distro backport status must be verified separately.
Mitigation direction
- Update to a kernel or distribution package containing the referenced stable commits.
- Check Linux distribution advisories for CVE-2022-49891-specific backports.
- Prioritize shared systems where untrusted local users have shell access.
- Restrict unnecessary local access to tracing or test-related kernel functionality where feasible.
Validation and detection
- Inventory Linux kernel versions across affected assets.
- Confirm vendor packages include the stable fixes or CVE backport.
- Review kernel advisory notes for affected version ranges in your distribution.
- Validate that no KEV or cited exploitation source exists before escalating urgency.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-49891 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/bef08acbe560a926b4cee9cc46404cc98ae5703bCVE reference, Linux
- https://git.kernel.org/stable/c/d1b6a8e3414aeaa0985139180c145d2d0fbd2a49CVE reference, Linux
- https://git.kernel.org/stable/c/71aeb8d01a8c7ab5cf7da3f81b35206f56ce6bcaCVE reference, Linux
- https://git.kernel.org/stable/c/66f0919c953ef7b55e5ab94389a013da2ce80a2cCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.