Skip to content
Sign in Sign up
JA EN FR
SecPulse
This page tracks the Ubuntu fix status. The vulnerability itself is described on the main CVE page. View CVE-2024-50175 →
Unrated

Vulnerability in linux-hwe-edge

UBUNTU-CVE-2024-50175 First seen on SecPulse

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2024-50175 has been found in linux-hwe-edge.
Risk of unauthorized operations or information disclosure.
What to do: upgrade linux-hwe-edge to 6.8.0-1023.25~22.04.1 or later.
If unsure, ask your IT team or search "linux-hwe-edge UBUNTU-CVE-2024-50175" on the vendor's site.

UBUNTU-CVE-2024-50175 (linux-hwe-edge)
Attack vector: local / no user interaction
Patched: 6.8.0-1023.25~22.04.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

What is the problem

A vulnerability (unclassified) exists in linux-hwe-edge.

Affected scope

Check the vendor advisory for the affected versions of linux-hwe-edge.

Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

How to fix

Update to 6.8.0-1023.25~22.04.1.

Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'linux-hwe-edge' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposureidentify
    grep -r 'linux-hwe-edge' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で linux-hwe-edge を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patchpatch
    Upgrade linux-hwe-edge to 6.8.0-1023.25~22.04.1

    ステージング環境で 6.8.0-1023.25~22.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verificationverify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

EcosystemPackageAffectedFixed
Ubuntu:16.04:LTS linux-hwe-edge
All versions
—
Ubuntu:18.04:LTS linux-aws-5.0
All versions
—
Ubuntu:18.04:LTS linux-aws-5.3
All versions
—
Ubuntu:18.04:LTS linux-azure
All versions
—
Ubuntu:18.04:LTS linux-azure-5.3
All versions
—
Ubuntu:18.04:LTS linux-azure-edge
All versions
—
Ubuntu:18.04:LTS linux-gcp
All versions
—
Ubuntu:18.04:LTS linux-gcp-5.3
All versions
—
Ubuntu:18.04:LTS linux-gke-4.15
All versions
—
Ubuntu:18.04:LTS linux-gke-5.4
All versions
—
Ubuntu:18.04:LTS linux-gkeop-5.4
All versions
—
Ubuntu:18.04:LTS linux-hwe
All versions
—
Ubuntu:18.04:LTS linux-oem
All versions
—
Ubuntu:18.04:LTS linux-oracle-5.0
All versions
—
Ubuntu:18.04:LTS linux-oracle-5.3
All versions
—
Ubuntu:20.04:LTS linux-aws-5.11
All versions
—
Ubuntu:20.04:LTS linux-aws-5.13
All versions
—
Ubuntu:20.04:LTS linux-aws-5.8
All versions
—
Ubuntu:20.04:LTS linux-azure-5.11
All versions
—
Ubuntu:20.04:LTS linux-azure-5.13
All versions
—
Ubuntu:20.04:LTS linux-azure-5.8
All versions
—
Ubuntu:20.04:LTS linux-azure-fde
All versions
—
Ubuntu:20.04:LTS linux-gcp-5.11
All versions
—
Ubuntu:20.04:LTS linux-gcp-5.13
All versions
—
Ubuntu:20.04:LTS linux-gcp-5.8
All versions
—
Ubuntu:20.04:LTS linux-gke
All versions
—
Ubuntu:20.04:LTS linux-gke-5.15
All versions
—
Ubuntu:20.04:LTS linux-hwe-5.11
All versions
—
Ubuntu:20.04:LTS linux-hwe-5.13
All versions
—
Ubuntu:20.04:LTS linux-hwe-5.8
All versions
—
Ubuntu:20.04:LTS linux-intel-5.13
All versions
—
Ubuntu:20.04:LTS linux-oem-5.10
All versions
—
Ubuntu:20.04:LTS linux-oem-5.13
All versions
—
Ubuntu:20.04:LTS linux-oem-5.14
All versions
—
Ubuntu:20.04:LTS linux-oem-5.6
All versions
—
Ubuntu:20.04:LTS linux-oracle-5.11
All versions
—
Ubuntu:20.04:LTS linux-oracle-5.13
All versions
—
Ubuntu:20.04:LTS linux-oracle-5.8
All versions
—
Ubuntu:20.04:LTS linux-raspi2
All versions
—
Ubuntu:20.04:LTS linux-riscv
All versions
—
Ubuntu:20.04:LTS linux-riscv-5.11
All versions
—
Ubuntu:20.04:LTS linux-riscv-5.8
All versions
—
Ubuntu:22.04:LTS linux-allwinner-5.19
All versions
—
Ubuntu:22.04:LTS linux-aws-5.19
All versions
—
Ubuntu:22.04:LTS linux-aws-6.2
All versions
—
Ubuntu:22.04:LTS linux-aws-6.5
All versions
—
Ubuntu:22.04:LTS linux-aws-6.8
< 6.8.0-1023.25~22.04.1
6.8.0-1023.25~22.04.1
Ubuntu:22.04:LTS linux-azure-5.19
All versions
—
Ubuntu:22.04:LTS linux-azure-6.2
All versions
—
Ubuntu:22.04:LTS linux-azure-6.5
All versions
—
Ubuntu:22.04:LTS linux-azure-6.8
< 6.8.0-1025.30~22.04.1
6.8.0-1025.30~22.04.1
Ubuntu:22.04:LTS linux-azure-fde-5.19
All versions
—
Ubuntu:22.04:LTS linux-azure-fde-6.2
All versions
—
Ubuntu:22.04:LTS linux-gcp-5.19
All versions
—
Ubuntu:22.04:LTS linux-gcp-6.2
All versions
—
Ubuntu:22.04:LTS linux-gcp-6.5
All versions
—
Ubuntu:22.04:LTS linux-gcp-6.8
< 6.8.0-1024.26~22.04.1
6.8.0-1024.26~22.04.1
Ubuntu:22.04:LTS linux-hwe-5.19
All versions
—
Ubuntu:22.04:LTS linux-hwe-6.2
All versions
—
Ubuntu:22.04:LTS linux-hwe-6.5
All versions
—
Ubuntu:22.04:LTS linux-hwe-6.8
< 6.8.0-57.59~22.04.1
6.8.0-57.59~22.04.1
Ubuntu:22.04:LTS linux-intel-iot-realtime
All versions
—
Ubuntu:22.04:LTS linux-lowlatency-hwe-5.19
All versions
—
Ubuntu:22.04:LTS linux-lowlatency-hwe-6.2
All versions
—
Ubuntu:22.04:LTS linux-lowlatency-hwe-6.5
All versions
—
Ubuntu:22.04:LTS linux-lowlatency-hwe-6.8
< 6.8.0-54.56.1~22.04.1
6.8.0-54.56.1~22.04.1
Ubuntu:22.04:LTS linux-nvidia-6.2
All versions
—
Ubuntu:22.04:LTS linux-nvidia-6.5
All versions
—
Ubuntu:22.04:LTS linux-nvidia-6.8
< 6.8.0-1022.25~22.04.2
6.8.0-1022.25~22.04.2
Ubuntu:22.04:LTS linux-oem-5.17
All versions
—
Ubuntu:22.04:LTS linux-oem-6.0
All versions
—
Ubuntu:22.04:LTS linux-oem-6.1
All versions
—
Ubuntu:22.04:LTS linux-oem-6.5
All versions
—
Ubuntu:22.04:LTS linux-oracle-6.5
All versions
—
Ubuntu:22.04:LTS linux-oracle-6.8
< 6.8.0-1020.21~22.04.1
6.8.0-1020.21~22.04.1
Ubuntu:22.04:LTS linux-realtime
All versions
—
Ubuntu:22.04:LTS linux-riscv
All versions
—
Ubuntu:22.04:LTS linux-riscv-5.19
All versions
—
Ubuntu:22.04:LTS linux-riscv-6.5
All versions
—
Ubuntu:22.04:LTS linux-riscv-6.8
< 6.8.0-53.55.1~22.04.1
6.8.0-53.55.1~22.04.1
Ubuntu:22.04:LTS linux-starfive-5.19
All versions
—
Ubuntu:22.04:LTS linux-starfive-6.2
All versions
—
Ubuntu:22.04:LTS linux-starfive-6.5
All versions
—
Ubuntu:24.04:LTS linux
< 6.8.0-54.56
6.8.0-54.56
Ubuntu:24.04:LTS linux-aws
< 6.8.0-1023.25
6.8.0-1023.25
Ubuntu:24.04:LTS linux-azure
< 6.8.0-1025.30
6.8.0-1025.30
Ubuntu:24.04:LTS linux-gcp
< 6.8.0-1024.26
6.8.0-1024.26
Ubuntu:24.04:LTS linux-gke
< 6.8.0-1019.23
6.8.0-1019.23
Ubuntu:24.04:LTS linux-gkeop
< 6.8.0-1006.8
6.8.0-1006.8
Ubuntu:24.04:LTS linux-ibm
< 6.8.0-1022.22
6.8.0-1022.22
Ubuntu:24.04:LTS linux-lowlatency
< 6.8.0-54.56.1
6.8.0-54.56.1
Ubuntu:24.04:LTS linux-nvidia
< 6.8.0-1022.25
6.8.0-1022.25
Ubuntu:24.04:LTS linux-nvidia-lowlatency
< 6.8.0-1022.25.2
6.8.0-1022.25.2
Ubuntu:24.04:LTS linux-oem-6.8
< 6.8.0-1024.24
6.8.0-1024.24
Ubuntu:24.04:LTS linux-oracle
< 6.8.0-1020.21
6.8.0-1020.21
Ubuntu:24.04:LTS linux-raspi
< 6.8.0-1019.23
6.8.0-1019.23
Ubuntu:24.04:LTS linux-realtime
All versions
—
Ubuntu:24.04:LTS linux-riscv
< 6.8.0-53.55.1
6.8.0-53.55.1
Ubuntu:Pro:Realtime:24.04:LTS linux-raspi-realtime
< 6.8.0-2018.19
6.8.0-2018.19
Ubuntu:Pro:Realtime:24.04:LTS linux-realtime
< 6.8.1-1016.17
6.8.1-1016.17
Original description The description as published by the source.

In the Linux kernel, the following vulnerability has been resolved: media: qcom: camss: Remove use_count guard in stop_streaming The use_count check was introduced so that multiple concurrent Raw Data Interfaces RDIs could be driven by different virtual channels VCs on the CSIPHY input driving the video pipeline. This is an invalid use of use_count though as use_count pertains to the number of times a video entity has been opened by user-space not the number of active streams. If use_count and stream-on count don't agree then stop_streaming() will break as is currently the case and has become apparent when using CAMSS with libcamera's released softisp 0.3. The use of use_count like this is a bit hacky and right now breaks regular usage of CAMSS for a single stream case. Stopping qcam results in the splat below, and then it cannot be started again and any attempts to do so fails with -EBUSY. [ 1265.509831] WARNING: CPU: 5 PID: 919 at drivers/media/common/videobuf2/videobuf2-core.c:2183 __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common] ... [ 1265.510630] Call trace: [ 1265.510636] __vb2_queue_cancel+0x230/0x2c8 [videobuf2_common] [ 1265.510648] vb2_core_streamoff+0x24/0xcc [videobuf2_common] [ 1265.510660] vb2_ioctl_streamoff+0x5c/0xa8 [videobuf2_v4l2] [ 1265.510673] v4l_streamoff+0x24/0x30 [videodev] [ 1265.510707] __video_do_ioctl+0x190/0x3f4 [videodev] [ 1265.510732] video_usercopy+0x304/0x8c4 [videodev] [ 1265.510757] video_ioctl2+0x18/0x34 [videodev] [ 1265.510782]…

Source: OSV.dev (Open Source Vulnerabilities) OSV

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details