data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2024-50289 in the interactive tracker

CVE-2024-50289

media: av7110: fix a spectre vulnerability

EPSS 0.2%

Published 2024-11-19 (23 months ago) by the Linux kernel CNA. Subsystem drivers/staging. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2024-50289 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormvulnerable6.1.190-1No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication.
Debian 13trixiefixed6.11.9-1Update the kernel and reboot. Fixed in 6.11.9-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed6.11.9-1Update the kernel and reboot. Fixed in 6.11.9-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed6.11.9-1Update the kernel and reboot. Fixed in 6.11.9-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

As warned by smatch: drivers/staging/media/av7110/av7110_ca.c:270 dvb_ca_ioctl() warn: potential spectre issue 'av7110->ci_slot' [w] (local cap) There is a spectre-related vulnerability at the code. Fix it.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/staging/media/av7110/av7110.h
drivers/staging/media/av7110/av7110_ca.c

What this is
MEDIA INPUT INFRASTRUCTURE (V4L/DVB)MAINTAINERS section matched on drivers/staging/media/ · linux-media@vger.kernel.org · Maintained
Kernel module
dvb_ttpci

Check it on the machine

grep -wE 'CONFIG_DVB_AV7110|CONFIG_STAGING' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w dvb_ttpci

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed. The build rule could not be established for 1 release, so nothing is claimed about those.

  • bookworm?
  • trixieMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armel/rpi, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, s390x/s390x
  • forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, loong64/loong64, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, s390x/s390x
?
not established - no Makefile entry for the affected file
M
a module where it is built at all; some flavours do not build it

Where a release above reads "not established", no build rule for the affected file was found in that release's kernel tree. That is a gap in this lookup, not a finding that the code is absent.

Build switches
CONFIG_DVB_AV7110, CONFIG_STAGING
Reads as
all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2024-11-19 (23 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.18%, higher than 6.9% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
drivers/staging

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
2.6.126.11.8f3927206c478
2.6.126.12458ea1c0be99

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2024-50289, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.