Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory-leak flaw in a TI K3 DMA driver error path. A local, low-privileged user may be able to trigger repeated failures that consume memory and affect availability. The sources do not show data theft, integrity impact, remote exploitation, or active exploitation.
Executive priority
Treat as a moderate availability risk, highest for embedded or appliance fleets using TI K3 platforms. It does not currently warrant emergency response based on the supplied evidence, but it should enter normal kernel patch cycles and local-user risk reviews.
Technical view
The issue is CWE-401 in dmaengine ti k3-udma-glue. If device_register() fails, the code must call put_device() so the dev_set_name() allocation can be freed through kobject cleanup. CVSS 3.1 is 5.5: local, low complexity, low privileges, no UI, availability high.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel builds with the TI K3 UDMA glue driver present or enabled. General Linux servers without this driver or hardware path are less likely exposed, but distribution backports should be verified.
Exploitation context
The bundle marks KEV as false and cites no active exploitation. The CVSS vector requires local access and low privileges. Impact is availability only, likely through memory exhaustion if the vulnerable failure path can be repeatedly reached.
Researcher notes
Evidence is limited to the CVE record and Linux stable commit references. The simplified affected-version data is ambiguous, so rely on vendor kernel advisories and commit backport status for exact exposure. Do not assume exploitability beyond local availability impact.
Mitigation direction
- Update to a kernel or vendor package containing the referenced stable fixes.
- If no vendor package is available, monitor Linux and distribution advisories for backports.
- Reduce exposure to untrusted local users on affected systems until patched.
- Review whether the TI K3 UDMA glue driver is needed and enabled.
Validation and detection
- Inventory kernel versions and distribution package patch levels across Linux assets.
- Check whether the TI K3 UDMA glue driver is built, loaded, or required.
- Map installed kernels against vendor advisories and the cited stable commits.
- Confirm no affected appliance or embedded Linux image is outside update coverage.
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-49860 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/1dd27541aa2b95bde71bddd43d73f9c16d73272cCVE reference, Linux
- https://git.kernel.org/stable/c/025eab5189fc7ee223ae9b4bc49d7df196543e53CVE reference, Linux
- https://git.kernel.org/stable/c/ac2b9f34f02052709aea7b34bb2a165e1853eb41CVE 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.