LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27075: media: dvb-frontends: avoid stack overflow warnings with clang

In the Linux kernel, the following vulnerability has been resolved: media: dvb-frontends: avoid stack overflow warnings with clang A previous patch worked around a KASAN issue in stv0367, now a similar problem showed up with clang: drivers/media/dvb-frontends/stv0367.c:1222:12: error: stack frame size (3624) exceeds limit (2048) in 'stv0367ter_set_frontend' [-Werror,-Wframe-larger-than] 1214 | static int stv0367ter_set_frontend(struct dvb_frontend *fe) Rework the stv0367_writereg() function to be simpler and mark both register access functions as noinline_for_stack so the temporary i2c_msg structures do not get duplicated on the stack when KASAN_STACK is enabled.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2024-27075 is a Linux kernel issue in the DVB frontend media driver code. The public record describes oversized kernel stack usage triggered by compiler and KASAN stack instrumentation, not a proven real-world attack. Business impact is mainly for systems running affected Linux kernels where this driver code is present.

Executive priority

Treat this as routine kernel maintenance unless the organization operates Linux systems with DVB/media driver exposure or compliance requires rapid CVE closure. There is no source-supported evidence of active exploitation, but kernel fixes should still be absorbed through normal patch cycles.

Technical view

The fix reworks stv0367 register access and marks register access functions noinline_for_stack to avoid duplicated temporary i2c_msg structures on the stack when KASAN_STACK is enabled. The CVE lists affected Linux kernel versions beginning at 4.16 and includes stable fix commits across supported branches.

Likely exposure

Exposure is most plausible on Linux systems using affected kernel versions with the media DVB frontend stv0367 driver built or available. Generic servers without DVB/media hardware may have limited practical exposure, but kernel package inventory is still needed.

Exploitation context

The provided sources do not show active exploitation, public exploit code, KEV listing, CVSS scoring, or a described attacker path. Evidence points to a kernel stack-size hardening or correctness fix rather than a clearly weaponized vulnerability.

Researcher notes

Key uncertainty is practical exploitability. The record names stack frame pressure with clang and KASAN_STACK, but does not provide an attack scenario, CWE, CVSS, or runtime impact. Validate branch-specific fix inclusion rather than relying only on upstream version labels.

Mitigation direction

  • Update to a kernel version containing the referenced stable fixes.
  • Use distribution kernel security updates where available, including Debian LTS guidance if applicable.
  • Check vendor advisories for exact package versions and reboot requirements.
  • If immediate patching is delayed, review whether the affected DVB frontend driver is enabled or loaded.

Validation and detection

  • Inventory running Linux kernel versions against the affected version ranges.
  • Confirm the kernel source or package includes the referenced stable fix commit for its branch.
  • Check whether stv0367 or related DVB frontend support is built, available, or loaded.
  • After updating, verify the system is booted into the fixed kernel.
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-27075 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
LinuxLinux3cd890dbe2a4f14cc44c85bb6cf37e5e22d4dd0e, 3cd890dbe2a4f14cc44c85bb6cf37e5e22d4dd0e, 3cd890dbe2a4f14cc44c85bb6cf37e5e22d4dd0e, 3cd890dbe2a4f14cc44c85bb6cf37e5e22d4dd0e, 3cd890dbe2a4f14cc44c85bb6cf37e5e22d4dd0e, 3cd890dbe2a4f14cc44c85bb6cf37e5e22d4dd0e, 3cd890dbe2a4f14cc44c85bb6cf37e5e22d4dd0e, 3cd890dbe2a4f14cc44c85bb6cf37e5e22d4dd0e, 3cd890dbe2a4f14cc44c85bb6cf37e5e22d4dd0e, dc4bc70259daba144f799e40a99413a86c601006, d1d85ae79d5e5592dccba6890658c0999b864ddc, ad91b2e392be4339e09eefd8479675b4232ddfa1, ec1eeaf5b6c12b561d9a90588987e44a2e2f8b1a, 4.4.168, 4.9.82, 4.14.20, 4.15.4unaffected
LinuxLinux4.16, 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.