Vulnerability · Published Apr 16, 2025 · Assigned by Linux
CVE-2025-22028media: vimc: skip .s_stream() for stopped entities
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 10% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: media: vimc: skip .s_stream() for stopped entities Syzbot reported [1] a warning prompted by a check in call_s_stream() that checks whether .s_stream() operation is warranted for unstarted or stopped subdevs. Add a simple fix in vimc_streamer_pipeline_terminate() ensuring that entities skip a call to .s_stream() unless they have been previously properly started. [1] Syzbot report: ------------[ cut here ]------------ WARNING: CPU: 0 PID: 5933 at drivers/media/v4l2-core/v4l2-subdev.c:460 call_s_stream+0x2df/0x350 drivers/media/v4l2-core/v4l2-subdev.c:460 Modules linked in: CPU: 0 UID: 0 PID: 5933 Comm: syz-executor330 Not tainted 6.13.0-rc2-syzkaller-00362-g2d8308bf5b67 #0 ... Call Trace: <TASK> vimc_streamer_pipeline_terminate+0x218/0x320 drivers/media/test-drivers/vimc/vimc-streamer.c:62 vimc_streamer_pipeline_init drivers/media/test-drivers/vimc/vimc-streamer.c:101 [inline] vimc_streamer_s_stream+0x650/0x9a0 drivers/media/test-drivers/vimc/vimc-streamer.c:203 vimc_capture_start_streaming+0xa1/0x130 drivers/media/test-drivers/vimc/vimc-capture.c:256 vb2_start_streaming+0x15f/0x5a0 drivers/media/common/videobuf2/videobuf2-core.c:1789 vb2_core_streamon+0x2a7/0x450 drivers/media/common/videobuf2/videobuf2-core.c:2348 vb2_streamon drivers/media/common/videobuf2/videobuf2-v4l2.c:875 [inline] vb2_ioctl_streamon+0xf4/0x170 drivers/media/common/videobuf2/videobuf2-v4l2.c:1118 __video_do_ioctl+0xaf0/0xf00 drivers/media/v4l2-core/v4l2-ioctl.c:3122 video_usercopy+0x4d2/0x1620 drivers/media/v4l2-core/v4l2-ioctl.c:3463 v4l2_ioctl+0x1ba/0x250 drivers/media/v4l2-core/v4l2-dev.c:366 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:906 [inline] __se_sys_ioctl fs/ioctl.c:892 [inline] __x64_sys_ioctl+0x190/0x200 fs/ioctl.c:892 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x250 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f2b85c01b19 ...
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | no fix listed | DEBIAN-CVE-2025-22028 |
| Debian:13 | linux | 6.12.25-1 | DEBIAN-CVE-2025-22028 |
| Debian:14 | linux | 6.12.25-1 | DEBIAN-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux | 6.8.0-86.87 | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux | 6.8.0-86.87 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-aws | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1041.43 | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-aws | 6.8.0-1041.43 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1041.43~22.04.1 | USN-7835-6 |
| Ubuntu:22.04:LTS | linux-aws-6.8 | 6.8.0-1041.43~22.04.1 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-azure | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1041.47 | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-azure | 6.8.0-1041.47 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-azure-6.11 | 6.11.0-1018.18~24.04.1 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1041.47~22.04.1 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-azure-6.8 | 6.8.0-1041.47~22.04.1 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-azure-fde | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:25.10 | linux-azure-fde | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | 6.8.0-1029.32 | USN-7940-2 |
| Ubuntu:24.04:LTS | linux-azure-nvidia | 6.8.0-1029.32 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-gcp | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1042.45 | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-gcp | 6.8.0-1042.45 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-gcp-6.11 | 6.11.0-1016.16~24.04.1 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1042.45~22.04.1 | USN-7835-3 |
| Ubuntu:22.04:LTS | linux-gcp-6.8 | 6.8.0-1042.45~22.04.1 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-gke | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1038.43 | USN-7835-3 |
| Ubuntu:24.04:LTS | linux-gke | 6.8.0-1038.43 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-gkeop | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1025.28 | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-gkeop | 6.8.0-1025.28 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-hwe-6.11 | 6.11.0-28.28~24.04.1 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-86.87~22.04.1 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-hwe-6.8 | 6.8.0-86.87~22.04.1 | USN-7835-4 |
| Ubuntu:22.04:LTS | linux-ibm | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1039.39 | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-ibm | 6.8.0-1039.39 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1039.39~22.04.1 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-ibm-6.8 | 6.8.0-1039.39~22.04.1 | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-intel | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-intel-iotg | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-kvm | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-lowlatency | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-86.87.1 | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-lowlatency | 6.8.0-86.87.1 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-lowlatency-hwe-6.11 | 6.11.0-1015.16~24.04.2 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-86.87.1~22.04.1 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-86.87.1~22.04.1 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-nvidia | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1041.44 | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-nvidia | 6.8.0-1041.44 | USN-7835-3 |
| Ubuntu:24.04:LTS | linux-nvidia-6.11 | 6.11.0-1012.12 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1041.44~22.04.2 | USN-7835-3 |
| Ubuntu:22.04:LTS | linux-nvidia-6.8 | 6.8.0-1041.44~22.04.2 | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1041.44.1 | USN-7835-3 |
| Ubuntu:24.04:LTS | linux-nvidia-lowlatency | 6.8.0-1041.44.1 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-nvidia-tegra | 6.8.0-1012.12 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-nvidia-tegra-igx | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-oem-6.11 | 6.11.0-1024.24 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-oem-6.8 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-oracle | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1038.39 | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-oracle | 6.8.0-1038.39 | USN-7835-1 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1038.39~22.04.1 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-oracle-6.8 | 6.8.0-1038.39~22.04.1 | USN-7835-5 |
| Ubuntu:22.04:LTS | linux-raspi | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1041.45 | USN-7887-2 |
| Ubuntu:24.04:LTS | linux-raspi | 6.8.0-1041.45 | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-riscv-6.8 | 6.8.0-86.87~22.04.1 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2025-22028 |
| Ubuntu:24.04:LTS | linux-xilinx | 6.8.0-1018.19 | UBUNTU-CVE-2025-22028 |
| Ubuntu:22.04:LTS | linux-xilinx-zynqmp | no fix listed | UBUNTU-CVE-2025-22028 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | adc589d2a20808fb99d46a78175cd023f2040338 – before a505075730d23ccc19fc4ac382a0ed73b630c057adc589d2a20808fb99d46a78175cd023f2040338 – before 845e9286ff99ee88cfdeb2b748f730003a512190adc589d2a20808fb99d46a78175cd023f2040338 – before 6f6064dab4dcfb7e34a395040a0c9dc22cc8765dadc589d2a20808fb99d46a78175cd023f2040338 – before 7a58d4c4cf8ff60ab1f93399deefaf6057da91c7adc589d2a20808fb99d46a78175cd023f2040338 – before 36cef585e2a31e4ddf33a004b0584a7a572246de77fbb561bb09f56877dd84318212da393909975f73236bf581e96eb48808fea522351ed81e24c9cce7ae48ae47227c0302b9f4b15a5bf45934a55673 |
| Linux | Linux | 5.1 |
References
- https://git.kernel.org/stable/c/a505075730d23ccc19fc4ac382a0ed73b630c057
- https://git.kernel.org/stable/c/845e9286ff99ee88cfdeb2b748f730003a512190
- https://git.kernel.org/stable/c/6f6064dab4dcfb7e34a395040a0c9dc22cc8765d
- https://git.kernel.org/stable/c/7a58d4c4cf8ff60ab1f93399deefaf6057da91c7
- https://git.kernel.org/stable/c/36cef585e2a31e4ddf33a004b0584a7a572246de