LiveActive security incident?Get immediate response
CVE Record

CVE-2024-43877: media: pci: ivtv: Add check for DMA map result

In the Linux kernel, the following vulnerability has been resolved: media: pci: ivtv: Add check for DMA map result In case DMA fails, 'dma->SG_length' is 0. This value is later used to access 'dma->SGarray[dma->SG_length - 1]', which will cause out of bounds access. Add check to return early on invalid value. Adjust warnings accordingly. Found by Linux Verification Center (linuxtesting.org) with SVACE.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-43877 is a Linux kernel bug in the ivtv PCI media driver. If DMA mapping fails, the driver can use a zero length value as an array index, causing out-of-bounds memory access. The sources do not provide CVSS, confirmed exploitation, or a full impact statement.

Executive priority

Handle through normal kernel patch management unless ivtv media hardware is deployed in production. Escalate priority for shared, exposed, or compliance-sensitive Linux systems where kernel memory-safety bugs carry higher operational risk.

Technical view

The ivtv driver fails to stop after a DMA mapping result leaves dma->SG_length at 0. Later code accesses dma->SGarray[dma->SG_length - 1], which underflows the index and can read or write outside the intended scatter-gather array. Stable kernel commits add an early invalid-value check.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds where the ivtv PCI media driver is present or usable. The bundle lists affected Linux kernel lines and stable fixes, but distribution-specific package status must be verified with the OS vendor.

Exploitation context

The provided sources do not show active exploitation, public exploit availability, or KEV listing. Practical exploitation details are not established in the bundle. Treat this as a kernel memory-safety issue with likely narrower exposure because it is tied to a specific media driver path.

Researcher notes

Evidence is strongest for root cause and fix direction, not exploitability. The finding was reported as found by Linux Verification Center with SVACE. No CWE, CVSS vector, exploit status, or complete distribution matrix is included in the source bundle.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for backported package versions.
  • Prioritize systems with ivtv-supported PCI media hardware or loaded modules.
  • If not needed, disable or remove access to the ivtv driver.
  • Track Debian LTS and kernel stable guidance for package-specific remediation.

Validation and detection

  • Inventory Linux kernel versions across affected fleets.
  • Check whether the ivtv module is present, loaded, or autoloadable.
  • Compare running kernels with vendor-fixed package versions.
  • Review kernel package changelogs for CVE-2024-43877 or ivtv DMA fixes.
  • Confirm updates through normal regression and reboot validation.
Prepared
Confidence
medium
Sources
9

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2024-43877 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
2ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4551236b55e80b2c1720b10b77e9400118b2339e, 66c8a83bf1de2eb3eea4734c7eda22255a965f11, 1932dc2f4cf6ac23e48e5fcc24d21adbe35691d1, 1932dc2f4cf6ac23e48e5fcc24d21adbe35691d1, 1932dc2f4cf6ac23e48e5fcc24d21adbe35691d1, 1932dc2f4cf6ac23e48e5fcc24d21adbe35691d1, 1b00b7335000c0e107f774cc8ee4d5340f824f28, 5.4.301unaffected
LinuxLinux5.16, 0, 6.1.103, 6.6.44, 6.10.3, 6.11affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.