Security readout for executives and security teams
Plain-English summary
A Linux camera-receiver driver can mishandle a buffer after a DMA startup failure, corrupt an internal list, and crash the kernel. The demonstrated outcome is a kernel panic, creating availability risk for affected embedded or camera-processing systems. The supplied CVSS score is 7.8, but exposure requires the specific TI J721E CSI2RX driver and relevant processing path.
Executive priority
Treat as an expedited reliability and availability issue where the affected TI camera-receiver hardware is deployed, especially in safety-sensitive or operationally critical devices. Systems without this driver or hardware are unlikely to be exposed. Request rapid asset identification first, then apply vendor-supported kernel updates according to operational risk.
Technical view
In ti_csi2rx_dma_callback(), a failed ti_csi2rx_start_dma() marked a buffer erroneous without removing it from the DMA queue. Retrying that buffer caused a second list_del(), list corruption, a kernel BUG, and panic. The published fix removes the buffer from the queue before vb2_buffer_done().
Likely exposure
Likely exposure is limited to Linux systems using the TI J721E CSI2RX media driver and exercising its DMA receive path. Embedded vision, camera, or industrial devices using this hardware deserve priority. The supplied version data is difficult to interpret as a complete range, so confirm exact exposure through kernel or distribution advisories and commit ancestry.
Exploitation context
The CVSS vector describes a local, low-complexity issue requiring low privileges and no user interaction. The source demonstrates a crash following DMA queue failure, but does not establish a practical attacker-controlled trigger. This CVE is not marked as CISA KEV, and the supplied sources provide no evidence of active exploitation or public weaponization.
Researcher notes
The failure is a double deletion from a kernel linked list after DMA restart failure. The supplied trace confirms list corruption and fatal panic, while confidentiality or integrity impact is not independently demonstrated despite the CVSS vector. Four stable-tree fixes are referenced. Exact affected boundaries and attacker triggerability remain insufficiently documented in the bundle.
Mitigation direction
- Update to a vendor-supported kernel containing the applicable stable fix commit.
- Confirm the device or distribution vendor's affected-version guidance before selecting a kernel release.
- Prioritize camera and embedded systems using the TI J721E CSI2RX driver.
- If immediate updating is impossible, seek vendor-approved operational workarounds; none are identified in the sources.
Validation and detection
- Inventory kernels and devices that include or load the TI J721E CSI2RX driver.
- Compare kernel commit ancestry against the four referenced stable fixes.
- Confirm camera workloads exercise the affected CSI2RX DMA path.
- After updating, verify vendor package versions and monitor logs for DMA failures, list corruption, or kernel panics.
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.
CVE-2025-38619 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
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
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:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/68e5579f4de12207b23c41b44a4c0778b6c2858fCVE reference, Linux
- https://git.kernel.org/stable/c/92d0188f36ca8082af7989d743eb5b44c2d259f7CVE reference, Linux
- https://git.kernel.org/stable/c/a4a8cb0889927d59ebd839458c8f038bc5298ef9CVE reference, Linux
- https://git.kernel.org/stable/c/ae42c6fe531425ef2f47e82f96851427d24bbf6bCVE 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.