LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27074: media: go7007: fix a memleak in go7007_load_encoder

In the Linux kernel, the following vulnerability has been resolved: media: go7007: fix a memleak in go7007_load_encoder In go7007_load_encoder, bounce(i.e. go->boot_fw), is allocated without a deallocation thereafter. After the following call chain: saa7134_go7007_init |-> go7007_boot_encoder |-> go7007_load_encoder |-> kfree(go) go is freed and thus bounce is leaked.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-27074 is a Linux kernel memory leak in the go7007 media driver. The bug can leave allocated firmware-loading memory behind when initialization fails or tears down. The public sources do not show active exploitation, remote reachability, or a scored severity, so urgency depends on whether affected kernels and this niche media driver path exist in your fleet.

Executive priority

Treat as a targeted kernel hygiene issue, not an emergency internet-wide exposure based on current sources. Patch through normal Linux maintenance unless you operate affected media capture hardware, custom kernels, or systems where kernel memory leaks could threaten availability.

Technical view

The issue is in go7007_load_encoder: go->boot_fw is allocated but not freed before the parent go structure is released through the documented saa7134_go7007_init to go7007_boot_encoder path. Linux stable commits resolve the leak across supported branches. The source bundle provides no CVSS, CWE, exploitability analysis, or attacker prerequisites.

Likely exposure

Likely limited to Linux systems running affected kernel builds with the go7007 media driver and related saa7134_go7007 initialization path present or usable. The sources do not identify network exposure, container breakout relevance, or affected distributions beyond kernel references and Debian LTS announcements.

Exploitation context

CISA KEV status is false in the source bundle, and no cited source states active exploitation. The bundle describes a memory leak, not code execution or privilege escalation. Operational impact would most plausibly be resource leakage, but the sources do not quantify triggerability, rate, or practical denial-of-service risk.

Researcher notes

Evidence is narrow: the CVE text identifies the leaking allocation and call chain, while Linux stable references indicate fixes. Missing data includes CVSS, precise exploit preconditions, attacker control, and distribution-specific fixed versions. Avoid assuming exploitability beyond the documented memory leak.

Mitigation direction

  • Apply vendor or distribution kernel updates containing the referenced Linux stable fixes.
  • Check Debian LTS or other distribution advisories for the corrected kernel package.
  • If patching is delayed, assess whether go7007-related media drivers are required.
  • Remove or disable unused affected media driver exposure according to vendor guidance.
  • Prioritize systems with physical media capture hardware or custom kernel builds.

Validation and detection

  • Inventory Linux kernel versions and compare them with vendor fixed releases.
  • Check whether go7007 and saa7134_go7007 driver code is built, loaded, or deployable.
  • Review distribution security advisories for CVE-2024-27074 package status.
  • Confirm patched kernels include one of the referenced stable commits or vendor backports.
  • Monitor affected hosts for unusual kernel memory growth if immediate patching is not possible.
Prepared
Confidence
medium
Sources
12

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-27074 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
12Source 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
LinuxLinux95ef39403f890360a3e48fe550d8e8e5d088ad74, 95ef39403f890360a3e48fe550d8e8e5d088ad74, 95ef39403f890360a3e48fe550d8e8e5d088ad74, 95ef39403f890360a3e48fe550d8e8e5d088ad74, 95ef39403f890360a3e48fe550d8e8e5d088ad74, 95ef39403f890360a3e48fe550d8e8e5d088ad74, 95ef39403f890360a3e48fe550d8e8e5d088ad74, 95ef39403f890360a3e48fe550d8e8e5d088ad74, 95ef39403f890360a3e48fe550d8e8e5d088ad74unaffected
LinuxLinux3.10, 0, 4.19.311, 5.4.273, 5.10.214, 5.15.153, 6.1.83, 6.6.23, 6.7.11, 6.8.2, 6.9affected
Weakness

CWE details

No CWE listed

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