CVE-2024-27075

media: dvb-frontends: avoid stack overflow warnings with clang

HIGH

7.8

CVSS Score

Published: May 1, 2024 at 01:04 PM UTC

Updated: June 17, 2026 at 07:19 AM UTC

2 products affected across 2 vendorsLinux KernelDebian Linux

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.8

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Debian Linux · Debiandrupal

95%

10.0

Linux Kernel · Linux

95%

v ≥ 4.14.20v ≥ 4.15.4v ≥ 4.4.168v ≥ 4.9.824.14.20 ≤ v < 4.154.15.4 ≤ v < 4.164.15.4 ≤ v < 4.19.3114.16 ≤ v < 4.19.3114.16 ≤ v < 5.10.2144.16 ≤ v < 5.15.1534.16 ≤ v < 5.4.2734.16 ≤ v < 6.1.834.16 ≤ v < 6.6.234.16 ≤ v < 6.7.114.16 ≤ v < 6.8.24.16 ≤ v < 6.94.20 ≤ v < 5.4.2734.4.168 ≤ v < 4.54.9.82 ≤ v < 4.105.11 ≤ v < 5.15.1535.16 ≤ v < 6.1.835.5 ≤ v < 5.10.2146.2 ≤ v < 6.6.236.7 ≤ v < 6.7.116.8 ≤ v < 6.8.23cd890dbe2a4f14cc44c85bb6cf37e5e22d4dd0e4.14.20 4.15.4 4.16 4.4.168 4.9.82ad91b2e392be4339e09eefd8479675b4232ddfa1d1d85ae79d5e5592dccba6890658c0999b864ddcdc4bc70259daba144f799e40a99413a86c601006ec1eeaf5b6c12b561d9a90588987e44a2e2f8b1a

Vendor states this is fixed in 107052a8cfeff3a97326277192b4f052e4860a8a (fixed)

Vendor states this is fixed in 7a4cf27d1f0538f779bf31b8c99eda394e277119 (fixed)

Vendor states this is fixed in 8fad9c5bb00d3a9508d18bbfe832e33a47377730 (fixed)

Vendor states this is fixed in c073c8cede5abd3836e83d70d72606d11d0759d4 (fixed)

Vendor states this is fixed in d20b64f156de5d10410963fe238d82a4e7e97a2f (fixed)

Vendor states this is fixed in d6b4895197ab5a47cb81c6852d49320b05052960 (fixed)

Vendor states this is fixed in ed514ecf4f29c80a2f09ae3c877059b401efe893 (fixed)

Vendor states this is fixed in fa8b472952ef46eb632825051078c21ce0cafe55 (fixed)

Vendor states this is fixed in fb07104a02e87c06c39914d13ed67fd8f839ca82 (fixed)

Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 4.16 (unaffected)

Vendor states this is fixed in 4.19.311 (unaffected)

Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 5.10.214 (unaffected)

Vendor states this is fixed in 5.15.153 (unaffected)

Vendor states this is fixed in 5.4.273 (unaffected)

Vendor states this is fixed in 6.1.83 (unaffected)

Vendor states this is fixed in 6.6.23 (unaffected)

Vendor states this is fixed in 6.7.11 (unaffected)

Vendor states this is fixed in 6.8.2 (unaffected)

Vendor states this is fixed in 6.9 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references